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
Aug 1, 2017, 17:38 UTC
Message-ID
<CAGZ79kY_NdBe1QjJWrLUkfDOk8Zrnopa945F1xBq=WFDNpRWMg@mail.gmail.com>
In-Reply-To
<1501603171.1671.8.camel@gmail.com>

On Tue, Aug 1, 2017 at 8:59 AM, Kaartic Sivaraam <kaarticsivaraam91196@gmail.com> wrote:

Show 11 quoted lines
> On Mon, 2017-07-31 at 13:23 -0700, Stefan Beller wrote:
>> 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.
>>
> I assume you mean the consistency in quoting i.e., you're expecting the
> patch to use (") instead of (') for quoting. Correct me, if I'm wrong.

Actually I did not imply any expectation on the outcome, because I do not know what the consistency end game looks like for this issue.

So maybe we'd want to go with the currently most used way? (Are there only three? (a) with dash, (b) with single quotes and (c) with double quotes?)

Show 18 quoted lines
>> >
>> > 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)
>>
> Man, I had no idea about people using two spaces after period.
>
>> 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.
>>
> Consistency is crucial. I'll just remove that part of the patch.
>
> --
> Kaartic
Previous: Kaartic SivaraamNext: Kaartic Sivaraam
Message 9 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.