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

Re: [PATCH 1/2] doc: fix small issues in SubmittingPatches

From
Stefan Beller <sbeller@google.com>
Date
Jul 31, 2017, 20:23 UTC
Message-ID
<CAGZ79kYg9jQ3kaKnNEJCH9fde=ar1KPiUr7=X+TguNc0Twqdzg@mail.gmail.com>
In-Reply-To
<20170730161816.2412-1-kaarticsivaraam91196@gmail.com>

On Sun, Jul 30, 2017 at 9:18 AM, Kaartic Sivaraam <kaarticsivaraam91196@gmail.com> wrote:

> Replace the dashed version of a command with undashed
> version and quote it.

I like it, but similar as below, we'd want to go for consistency.

>
> Further, remove duplicated space character.

https://en.wikipedia.org/wiki/Sentence_spacing seems like a globally controversial thing. (I assumed it was some sort of local dialect before researching it properly)

I personally do not mind one way or another regarding (double) spaces after a period, but I would think we'd strive for consistency throughout the project.

Show 31 quoted lines
>
> Signed-off-by: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
> ---
>  Documentation/SubmittingPatches | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index 558d465b6..9d0dab08d 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -293,7 +293,7 @@ then you just add a line saying
>
>          Signed-off-by: Random J Developer <random@developer.example.org>
>
> -This line can be automatically added by Git if you run the git-commit
> +This line can be automatically added by Git if you run the 'git commit'
>  command with the -s option.
>
>  Notice that you can place your own Signed-off-by: line when
> @@ -366,7 +366,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 maintainer and cc the list.
> +     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'.
> --
> 2.14.0.rc1.434.g6eded367a
>
Previous: Kaartic SivaraamNext: Junio C Hamano
Message 6 of 23 in “doc: fix small issues in SubmittingPatches”
  1. 1/2 doc: fix small issues in SubmittingPatchesKaartic Sivaraam, Jul 30, 2017
  2. 2/2 doc: add another way to identify if a patch has been mergedKaartic Sivaraam, Jul 30, 2017
  3. Philip OakleyJul 30, 2017
  4. Kaartic SivaraamJul 30, 2017
  5. 1/2 doc: fix small issues in SubmittingPatchesKaartic Sivaraam, Jul 30, 2017
  6. Stefan BellerJul 31, 2017
  7. Junio C HamanoJul 31, 2017
  8. Kaartic SivaraamAug 1, 2017
  9. Stefan BellerAug 1, 2017
  10. Kaartic SivaraamAug 2, 2017
  11. Junio C HamanoAug 2, 2017
  12. Stefan BellerAug 2, 2017
  13. Kaartic SivaraamAug 3, 2017
  14. 1/2 doc: fix small issues in SubmittingPatchesKaartic Sivaraam, Aug 1, 2017
  15. 2/2 doc: add another way to identify if a patch has been mergedKaartic Sivaraam, Aug 1, 2017
  16. Stefan BellerAug 1, 2017
  17. Kaartic SivaraamAug 2, 2017
  18. Junio C HamanoAug 2, 2017
  19. Junio C HamanoAug 2, 2017
  20. Stefan BellerAug 2, 2017
  21. Kaartic SivaraamAug 7, 2017
  22. Kaartic SivaraamAug 7, 2017
  23. Philip OakleyAug 1, 2017

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.