git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] SubmittingPatches: fix an inconsistency

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 13, 2014, 18:20 UTC
Message-ID
<xmqqy4rf0xod.fsf@gitster.dls.corp.google.com>
In-Reply-To
<5463FB4C.2060203@inventati.org>
slavomir vlcek <svlc@inventati.org> writes:
Show 27 quoted lines
> The 'SubmittingPatches' document contains a small inconsistency
>  in a patch-email sending procedure.
>
> Not a big thing,
> but a newcomer could get confused.
>
> Please,
> also consider adding the definition/explanation for all the branches available
> at the beginning of this document (and maybe even what their names stand for).
> Thanks.
>
> Signed-off-by: slavomir vlcek <svlc@inventati.org>
> ---
>
> From 74859712cf805663e3863686bdc09511c74b207b Mon Sep 17 00:00:00 2001
> From: slavomir vlcek <svlc@inventati.org>
> Date: Thu, 13 Nov 2014 00:18:39 +0100
> Subject: [PATCH] SubmittingPatches: fix an inconsistency
>
> At line 213 there was an instruction:
>   "re-send it with "To:" set to the maintainer [*1*] and "cc:" the list [*2*]"
>
> and this instruction got repeated once more in the document (line 340):
>   "Send it to the list and cc the maintainer."
>
> This inconsistency was solved by editing the second occurance.
> ---
The same comment applies to the log message part.
Will queue; no need to resend.
Thanks.
Show 16 quoted lines
>  Documentation/SubmittingPatches | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index e6d46ed..fa71b5f 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -337,7 +337,7 @@ suggests to the contributors:
>       spend their time to improve your patch.  Go back to step (2).
>  
>   (4) The list forms consensus that the last round of your patch is
> -     good.  Send it to the list and cc the maintainer.
> +     good.  Send it to the maintainer and cc the list.
>  
>   (5) A topic branch is created with the patch and is merged to 'next',
>       and cooked further and eventually graduates to 'master'.
Previous: slavomir vlcekNext: Junio C Hamano
Message 3 of 9 in “builtin: move builtin retrieval to get_builtin()”
  1. builtin: move builtin retrieval to get_builtin()slavomir vlcek, Nov 12, 2014
  2. SubmittingPatches: fix an inconsistencyslavomir vlcek, Nov 13, 2014
  3. Junio C HamanoNov 13, 2014
  4. Junio C HamanoNov 13, 2014
  5. Junio C HamanoNov 13, 2014
  6. slavomir vlcekNov 13, 2014
  7. Junio C HamanoNov 13, 2014
  8. Slavomir VlcekNov 16, 2014
  9. Junio C HamanoNov 17, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.