From 1b586585f5e6647642979fa9e0641aad3bcea924 Mon Sep 17 00:00:00 2001 From: Tuomas Ahola Date: Thu, 17 Sep 2026 13:21:04 +0300 Subject: [PATCH] fixup! CONTRIBUTING.md: add guide for first-time contributors The upstream Git project changed the guidance in 16b2924aab (MyFirstContribution: recommend shallow threading of cover letters, 2026-06-15) to prefer arrangement where all cover letters are direct replies to the v1 cover letter. Update CONTRIBUTING.md to reflect that. While at it, replace (at times unresponsive) public-inbox.org links with links to lore.kernel.org. Signed-off-by: Tuomas Ahola --- CONTRIBUTING.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 48ff9029374df3..ddd0836fa05ab6 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -96,7 +96,7 @@ you can fix quickly, or if anything catches your eye. You can also look at [the unofficial Chromium issues page](https://crbug.com/git) for multi-platform issues. You can look at recent user questions on -[the Git mailing list](https://public-inbox.org/git). +[the Git mailing list](https://lore.kernel.org/git). Or you can "scratch your own itch", i.e. address an issue you have with Git. The team at Microsoft where the Git for Windows maintainer works, for example, is focused almost entirely on [improving performance](https://blogs.msdn.microsoft.com/devops/2018/01/11/microsofts-performance-contributions-to-git-in-2017/). We approach our work by finding something that is slow and try to speed it up. We start our @@ -332,7 +332,7 @@ Submit Your Patch Git for Windows [accepts pull requests on GitHub](https://github.com/git-for-windows/git/pulls), but these are reserved for Windows-specific improvements. For core Git, submissions are accepted on -[the Git mailing list](https://public-inbox.org/git). +[the Git mailing list](https://lore.kernel.org/git). ### Configure Git to Send Emails @@ -367,8 +367,8 @@ To construct a patch set, use the `git format-patch` command. There are three im `git branch --edit-description`, you will end up with a 0/N mail with that description and a nice overall diffstat. * `--in-reply-to=[Message-ID]`: This will mark your cover letter as replying to the given - message (which should correspond to your previous iteration). To determine the correct Message-ID, - find the message you are replying to on [public-inbox.org/git](https://public-inbox.org/git) and take + message (which should correspond to your first iteration). To determine the correct Message-ID, + find the message you are replying to on [lore.kernel.org/git](https://lore.kernel.org/git) and take the ID from between the angle brackets. * `--subject-prefix=[prefix]`: This defaults to [PATCH]. For subsequent iterations, you will want to @@ -413,5 +413,5 @@ To submit a nth version patch (say version 3): ``` git send-email --to=git@vger.kernel.org --cc= --cc= \ - --in-reply-to= [dir with patches]/*.patch + --in-reply-to= [dir with patches]/*.patch ```