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

Re: [PATCH 3/7] Documentation: git-init: template directory: reword

From
Linus Arver <linusarver@gmail.com>
Date
Aug 8, 2014, 16:36 UTC
Message-ID
<20140808163652.GA791@k0>
In-Reply-To
<xmqqwqalmt42.fsf@gitster.dls.corp.google.com>
On Wed, Aug 06, 2014 at 10:21:33AM -0700, Junio C Hamano wrote:
Show 20 quoted lines
> Linus Arver <linusarver@gmail.com> writes:
> 
> > No, the unindenting/removal of blank lines is a non-grammar change and
> > is not necessary, as it doesn't have any effect on the actual output
> > (html/txt/manpage).
> >
> > I can either keep the same coding style with the rewording, or chop this
> > into two commits, one for the rewording and another for reformatting.
> > Which one do you suggest?
> 
> If I were doing this change, I wouldn't touch the formatting,
> because I did not find that the reformatted version would be any
> easier to read or maintain compared to the original.
> 
> But I suspect that you must have thought the reformatting was a good
> thing to do for a reason, and I suspected I might have been missing
> something obvious to you, and that was why I asked.  If there is a
> good reason to reformat, then lets hear it in the commit log message
> of one of the two patches.  Otherwise we can drop the reformatting
> part.

And well, considering that the rewording makes the separate items into a single sentence, I thought it would help readability to delete all the whitespace.

In retrospect, I don't think this is a good enough reason to reformat. It was more of a personal writing style judgment call. I am dropping the reformatting part.

Previous: Junio C HamanoNext: Linus Arver
Message 10 of 30 in “lots of documentation fixes/rewordings in git-init(1)”
  1. lots of documentation fixes/rewordings in git-init(1)Linus Arver, Aug 2, 2014
  2. 1/7 Documentation: git-init: typographical fixesLinus Arver, Aug 2, 2014
  3. Junio C HamanoAug 5, 2014
  4. Linus ArverAug 6, 2014
  5. 2/7 Documentation: git-init: list items faceliftLinus Arver, Aug 2, 2014
  6. 3/7 Documentation: git-init: template directory: rewordLinus Arver, Aug 2, 2014
  7. Junio C HamanoAug 5, 2014
  8. Linus ArverAug 6, 2014
  9. Junio C HamanoAug 6, 2014
  10. Linus ArverAug 8, 2014
  11. 4/7 Documentation: git-init: --separate-git-dir: clarifyLinus Arver, Aug 2, 2014
  12. Junio C HamanoAug 5, 2014
  13. Linus ArverAug 6, 2014
  14. Junio C HamanoAug 6, 2014
  15. Linus ArverAug 8, 2014
  16. 5/7 Documentation: git-init: reword parenthetical statementsLinus Arver, Aug 2, 2014
  17. 6/7 Documentation: git-init: template directory: reword and cross-referenceLinus Arver, Aug 2, 2014
  18. 7/7 Documentation: git-init: flesh out exampleLinus Arver, Aug 2, 2014
  19. Junio C HamanoAug 5, 2014
  20. Linus ArverAug 6, 2014
  21. Junio C HamanoAug 6, 2014
  22. Linus ArverAug 8, 2014
  23. lots of documentation fixes/rewordings in git-init(1)Linus Arver, Aug 8, 2014
  24. 1/7 Documentation: git-init: typographical fixesLinus Arver, Aug 8, 2014
  25. 2/7 Documentation: git-init: list items faceliftLinus Arver, Aug 8, 2014
  26. 3/7 Documentation: git-init: template directory: rewordLinus Arver, Aug 8, 2014
  27. 4/7 Documentation: git-init: --separate-git-dir: clarifyLinus Arver, Aug 8, 2014
  28. 5/7 Documentation: git-init: reword parenthetical statementsLinus Arver, Aug 8, 2014
  29. 6/7 Documentation: git-init: template directory: reword and cross-referenceLinus Arver, Aug 8, 2014
  30. 7/7 Documentation: git-init: flesh out exampleLinus Arver, Aug 8, 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.