Re: [PATCH v3] MyFirstContribution: add note on confirming patches

From: Queen Jessa <qjessa662@gmail.com>
Date: Oct 27, 2025, 17:09 UTC
Message-ID: <CA+JX8Fq-7Vy7TXB4cfxCJNouBAYzjyaqtA-mxSiGUiNm1DRs8Q@mail.gmail.com>
In-Reply-To: <xmqq4irkjpek.fsf@gitster.g>

okay. Thank you

On Mon, Oct 27, 2025 at 5:11 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 45 quoted lines

>
> 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
>