diff options
Diffstat (limited to '34.md')
| -rw-r--r-- | 34.md | 10 |
1 files changed, 5 insertions, 5 deletions
| @@ -70,9 +70,9 @@ The `refs` tag can be optionally extended to enable clients to identify how many | |||
| 70 | 70 | ||
| 71 | Patches can be sent by anyone to any repository. Patches to a specific repository SHOULD be sent to the relays specified in that repository's announcement event's `"relays"` tag. Patch events SHOULD include an `a` tag pointing to that repository's announcement address. | 71 | Patches can be sent by anyone to any repository. Patches to a specific repository SHOULD be sent to the relays specified in that repository's announcement event's `"relays"` tag. Patch events SHOULD include an `a` tag pointing to that repository's announcement address. |
| 72 | 72 | ||
| 73 | Patches in a patch set SHOULD include a NIP-10 `e` `reply` tag pointing to the previous patch. | 73 | Patches in a patch set SHOULD include a [NIP-10](10.md) `e` `reply` tag pointing to the previous patch. |
| 74 | 74 | ||
| 75 | The first patch revision in a patch revision SHOULD include a NIP-10 `e` `reply` to the original root patch. | 75 | The first patch revision in a patch revision SHOULD include a [NIP-10](10.md) `e` `reply` to the original root patch. |
| 76 | 76 | ||
| 77 | ```jsonc | 77 | ```jsonc |
| 78 | { | 78 | { |
| @@ -125,7 +125,7 @@ Issues may have a `subject` tag, which clients can utilize to display a header. | |||
| 125 | 125 | ||
| 126 | ## Replies | 126 | ## Replies |
| 127 | 127 | ||
| 128 | Replies to either a `kind:1621` _issue_ or a `kind:1617` _patch_ event should follow [NIP-22 comment](22.md). | 128 | Replies to either a `kind:1621` (_issue_) or a `kind:1617` (_patch_) event should follow [NIP-22 comment](22.md). |
| 129 | 129 | ||
| 130 | ## Status | 130 | ## Status |
| 131 | 131 | ||
| @@ -161,9 +161,9 @@ Root Patches and Issues have a Status that defaults to 'Open' and can be set by | |||
| 161 | } | 161 | } |
| 162 | ``` | 162 | ``` |
| 163 | 163 | ||
| 164 | The Status event with the largest created_at date is valid. | 164 | The most recent Status event (by `created_at` date) from either the issue/patch author or a maintainer is considered valid. |
| 165 | 165 | ||
| 166 | The Status of a patch-revision defaults to either that of the root-patch, or `1632` (Closed) if the root-patch's Status is `1631` and the patch-revision isn't tagged in the `1631` event. | 166 | The Status of a patch-revision defaults to either that of the root-patch, or `1632` (_Closed_) if the root-patch's Status is `1631` (_Applied/Merged_) and the patch-revision isn't tagged in the `1631` (_Applied/Merged_) event. |
| 167 | 167 | ||
| 168 | 168 | ||
| 169 | ## Possible things to be added later | 169 | ## Possible things to be added later |