diff options
| author | David Bremner <david@tethera.net> | 2026-06-24 07:16:27 +0900 |
|---|---|---|
| committer | David Bremner <david@tethera.net> | 2026-06-24 07:16:27 +0900 |
| commit | 4406acec85aafc12e0c6abfa75a0df0f1cf3dd2f (patch) | |
| tree | 3fc27b8a8dd76190e9291dd2ddf1ec6b08c930a6 | |
| parent | 931c348a208b7bce27f86d69127d13cf0a9a31c6 (diff) | |
update links to git.notmuchmail.org on contributing page
| -rw-r--r-- | contributing.mdwn | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/contributing.mdwn b/contributing.mdwn index c8d6f5c..db77e20 100644 --- a/contributing.mdwn +++ b/contributing.mdwn @@ -62,7 +62,7 @@ achieve. You may prefix the subjects of such patches with "RFC" or The Notmuch code base follows a fairly uniform coding style. See the existing code around your changes, and read -[`devel/STYLE`](https://git.notmuchmail.org/git/notmuch/blob/HEAD:/devel/STYLE) +[`devel/STYLE`](https://git.notmuchmail.org/git/notmuch/tree/devel/STYLE) in the Notmuch source. It's not difficult to get it right, and may save you an extra review round. @@ -113,7 +113,7 @@ easy to confirm your changes actually fix the issue. Some people use this approach also for adding new features. See -[`test/README`](https://git.notmuchmail.org/git/notmuch/blob/HEAD:/test/README) +[`test/README`](https://git.notmuchmail.org/git/notmuch/tree/test/README) in the Notmuch source for further information. ## Update the documentation @@ -131,7 +131,7 @@ much as possible, try to be consistent between modes. ## Update NEWS If you make user visible changes, you should add an entry to the -[`NEWS`](https://git.notmuchmail.org/git/notmuch/blob/HEAD:/NEWS) file. +[`NEWS`](https://git.notmuchmail.org/git/notmuch/tree/NEWS) file. In practice adding NEWS items can be done later during the release process, but then you typically get a one line mention, if at all. |