memory-leaks

commit 8cd09caa1e3bf44929b093757b829821a5e74fb2
parent 44812802133560839a572314731363e2b8334f03
Author: Kévin Le Gouguec <kevin.legouguec@gmail.com>
Date:   Wed, 14 Jan 2026 07:58:01 +0100

Mull over email patch practices

Prompted by <https://lwn.net/Articles/1053889/> and
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=20f75db8521aebfa48b563b0298175ed68e3bae8>
.

Diffstat:
M
guides/applications/git/send-email.org
 | 
52
++++++++++++++++++++++++++++++++++++++++++++++++++++

1 file changed, 52 insertions(+), 0 deletions(-)
diff --git a/guides/applications/git/send-email.org b/guides/applications/git/send-email.org
@@ -1,3 +1,55 @@
+* Conventions
+** Threading revisions
+Depends on project preference.  Consider:
+
+- the [[https://git-scm.com/docs/MyFirstContribution#v2-git-send-email][Git project's guidelines]]: set =--in-reply-to= for version $n$ to
+  the Message-ID for version $n-1$'s cover letter.
+  #+begin_quote
+You will also need to go and find the Message-ID of your previous
+cover letter. You can either note it when you send the first series,
+from the output of =git= =send-email=, or you can look it up on the
+[[https://lore.kernel.org/git][mailing list]]. Find your cover letter in the archives, click on it,
+then click "permalink" or "raw" to reveal the Message-ID header. It
+should match:
+
+#+begin_example
+Message-ID: <foo.12345.author@example.com>
+#+end_example
+
+Your Message-ID is =<foo.12345.author@example.com>=. This example will
+be used below as well; make sure to replace it with the correct
+Message-ID for your *previous cover letter* - that is, if you're
+sending v2, use the Message-ID from v1; if you're sending v3, use the
+Message-ID from v2.
+  #+end_quote
+
+- the [[https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/CONTRIBUTING.d/patches/sendmail][Linux man-pages project's guidelines]]: set =--in-reply-to= for
+  version $n$ to the Message-ID for version $1$'s cover letter.
+  #+begin_example
+    In-Reply-To
+	Revisions of a patch or patch set should reply to the cover
+	letter of the first iteration of the patch set.  If there was no
+	cover letter, they should reply to the first patch.  Example:
+
+		[PATCH v1 00] ...
+		├─> [PATCH v1 01] ...
+		├─> [PATCH v1 02] ...
+		├─> [PATCH v1 03] ...
+		├─> [PATCH v2 00] ...
+		│ ├─> [PATCH v2 01] ...
+		│ ├─> [PATCH v2 02] ...
+		│ └─> [PATCH v2 03] ...
+		└─> [PATCH v3 00] ...
+		  ├─> [PATCH v3 01] ...
+		  ├─> [PATCH v3 02] ...
+		  └─> [PATCH v3 03] ...
+  #+end_example
+
+- the [[https://docs.kernel.org/process/submitting-patches.html#explicit-in-reply-to-headers][Linux project's guidelines]]: avoid setting =In-Repy-To= at all;
+  prefer =Link= trailers; [[https://lwn.net/Articles/1037069/][contentious]] though.
+
+On the tool side, [[https://b4.docs.kernel.org/en/latest/config.html#:~:text=b4.send-same-thread][b4 supports all conventions]] via
+=b4.send-same-thread=.  The default is not to thread at all.
 * =.authinfo.gpg=
 ** Step 1: Install ~git-credential-netrc~
 AFAICT not all distributions package this script?  As far as those I