From: Junio C Hamano <gitster@pobox.com>
To: Queen Jessa <qjessa662@gmail.com>
Cc: git@vger.kernel.org, christian.couder@gmail.com,
usmanakinyemi202@gmail.com
Subject: Re: [PATCH v3] MyFirstContribution: add note on confirming patches
Date: Mon, 27 Oct 2025 09:11:15 -0700 [thread overview]
Message-ID: <xmqq4irkjpek.fsf@gitster.g> (raw)
In-Reply-To: <xmqq8qgwjpo5.fsf@gitster.g> (Junio C. Hamano's message of "Mon, 27 Oct 2025 09:05:30 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> I can make the author identity and sign-off of the version I queue
> consistent locally before applying to save an extra patch exchange,
> of course. But now I am not sure if I understand your preference
> correctly.
For now, I'll queue the following for this topic. Thanks!
----- >8 -----
From: Queen Ediri Jessa <qjessa662@gmail.com>
Date: Mon, 27 Oct 2025 12:16:00 +0100
Subject: [PATCH] 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>
---
Documentation/MyFirstContribution.adoc | 5 +++++
1 file changed, 5 insertions(+)
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
--
2.51.2-678-g0cd646409c
next prev parent reply other threads:[~2025-10-27 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 11:16 [PATCH v3] MyFirstContribution: add note on confirming patches QueenJcloud
2025-10-27 15:09 ` Junio C Hamano
2025-10-27 15:50 ` Queen Jessa
2025-10-27 16:05 ` Junio C Hamano
2025-10-27 16:11 ` Junio C Hamano [this message]
2025-10-27 17:09 ` Queen Jessa
2025-10-27 17:18 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq4irkjpek.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=qjessa662@gmail.com \
--cc=usmanakinyemi202@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).