aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorQueen Ediri Jessa <qjessa662@gmail.com>2025-10-27 12:16:00 +0100
committerJunio C Hamano <gitster@pobox.com>2025-10-27 09:09:53 -0700
commit29181abeadb20421ffa39c1b6a51c0d59598b9d6 (patch)
treed67ff53aa187f39b31555b7d383215e00f063203
parent419c72cb8ada252b260efc38ff91fe201de7c8c3 (diff)
downloadgit-29181abeadb20421ffa39c1b6a51c0d59598b9d6.tar.gz
MyFirstContribution: add note on confirming patches
Add a note after the `git send-email` section explaining how contributors can confirm that their patches reached the mailing list by checking https://lore.kernel.org/git/. This helps contributors verify that their emails were successfully delivered. Signed-off-by: Queen Ediri Jessa <qjessa662@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/MyFirstContribution.adoc5
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc
index 02ba8ba5f6..f186dfbc89 100644
--- a/Documentation/MyFirstContribution.adoc
+++ b/Documentation/MyFirstContribution.adoc
@@ -1153,6 +1153,11 @@ NOTE: When you are sending a real patch, it will go to git@vger.kernel.org - but
please don't send your patchset from the tutorial to the real mailing list! For
now, you can send it to yourself, to make sure you understand how it will look.
+NOTE: After sending your patches, you can confirm that they reached the mailing
+list by visiting https://lore.kernel.org/git/. Use the search bar to find your
+name or the subject of your patch. If it appears, your email was successfully
+delivered.
+
After you run the command above, you will be presented with an interactive
prompt for each patch that's about to go out. This gives you one last chance to
edit or quit sending something (but again, don't edit code this way). Once you