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

Aw: Re: [PATCH 05/13] Fix some typos

From
Thomas Ackermann <th.acker@arcor.de>
Date
Aug 25, 2013, 09:13 UTC
Message-ID
<892787868.481320.1377421991470.JavaMail.ngmail@webmail16.arcor-online.net>
In-Reply-To
<20130825050159.GH2882@elie.Belkin>
Show 13 quoted lines
> >  
> > -Or you can use linkgit:git-name-rev[1], which will give the commit a
> > +or you can use linkgit:git-name-rev[1], which will give the commit a
> 
> I think this reads better with a capital 'O'.  (The pedant in me
> likes it, too, since a colon ends a sentence.)
> 
> The lowercase 'but' later in this section should perhaps also be
> capitalized, since it also starts an independent thought.
> 
> 	But that may sometimes help you guess which tags come after the
> 	given commit.
>

I am no native speaker, but I am a little reluctant to start a new sentence with "But" or "Or".

Show 17 quoted lines
> The sentence "So, you can run something like ... then search for a
> line that looks like ..." is a sequence of incomplete thoughts.  It
> could be paraphrased a little to scan better:
> 
> 	So, if you run something like "git show-branch e05db0fd
> 	v1.5.0-rc0 v1.5.0-rc1 v1.5.0-rc2"
> 
> 		$ git show-branch e05db0fd v1.5.0-rc0 v1.5.0-rc1 v1.5.0-rc2
> 		! [e05db...
> 
> 	then a line like
> 
> 		+ ++ [e05db0fd] Fix warnings in ...
> 
> 	shows that e05db0fd is reachable from itself, from v1.5.0-rc1,
> 	and from v1.5.0-rc2, and not from v1.5.0-rc0.
> 
OK; thanks! I will add this.
Show 6 quoted lines
> >  
> > -To see how submodule support works, create (for example) four example
> > +To see how submodule support works, create four example
> 
> I'd keep the joke.
>
I totally missed the joke ...

--- Thomas

Previous: Jonathan NiederNext: Thomas Ackermann
Message 17 of 44 in “Modernize user-manual”
  1. 0/13 Modernize user-manualThomas Ackermann, Aug 24, 2013
  2. 01/13 Call it "Git User Manual" and remove reference to very old Git versionThomas Ackermann, Aug 24, 2013
  3. Jonathan NiederAug 25, 2013
  4. Junio C HamanoAug 25, 2013
  5. 02/13 Use current "detached HEAD" messageThomas Ackermann, Aug 24, 2013
  6. Jonathan NiederAug 25, 2013
  7. Aw: Re: [PATCH 02/13] Use current "detached HEAD" messageThomas Ackermann, Aug 25, 2013
  8. 03/13 Use current output for "git repack"Thomas Ackermann, Aug 24, 2013
  9. Jonathan NiederAug 25, 2013
  10. Aw: Re: [PATCH 03/13] Use current output for "git repack"Thomas Ackermann, Aug 25, 2013
  11. 04/13 Use "git merge" instead of "git pull ."Thomas Ackermann, Aug 24, 2013
  12. Junio C HamanoAug 25, 2013
  13. Jonathan NiederAug 25, 2013
  14. Martin von ZweigbergkAug 25, 2013
  15. 05/13 Fix some typosThomas Ackermann, Aug 24, 2013
  16. Jonathan NiederAug 25, 2013
  17. Aw: Re: [PATCH 05/13] Fix some typosThomas Ackermann, Aug 25, 2013
  18. 06/13 Simplify "How to make a commit"Thomas Ackermann, Aug 24, 2013
  19. Junio C HamanoAug 25, 2013
  20. Jonathan NiederAug 25, 2013
  21. Aw: Re: [PATCH 06/13] Simplify "How to make a commit"Thomas Ackermann, Aug 25, 2013
  22. 07/13 Improve description in "How to merge"Thomas Ackermann, Aug 24, 2013
  23. Junio C HamanoAug 25, 2013
  24. Jonathan NiederAug 25, 2013
  25. Aw: Re: [PATCH 07/13] Improve description in "How to merge"Thomas Ackermann, Aug 25, 2013
  26. 08/13 Improve section "Manipulating branches"Thomas Ackermann, Aug 24, 2013
  27. Junio C HamanoAug 25, 2013
  28. Aw: Re: [PATCH 08/13] Improve section "Manipulating branches"Thomas Ackermann, Aug 25, 2013
  29. 09/13 Improve section "Merge multiple trees"Thomas Ackermann, Aug 24, 2013
  30. Jonathan NiederAug 25, 2013
  31. Aw: Re: [PATCH 09/13] Improve section "Merge multiple trees"Thomas Ackermann, Aug 25, 2013
  32. Jonathan NiederAug 25, 2013
  33. 10/13 Remove unnecessary historical note from "Object storage format"Thomas Ackermann, Aug 24, 2013
  34. Junio C HamanoAug 25, 2013
  35. 11/13 Remove obscure reference from "Examples"Thomas Ackermann, Aug 24, 2013
  36. Junio C HamanoAug 25, 2013
  37. Jonathan NiederAug 25, 2013
  38. Aw: Re: [PATCH 11/13] Remove obscure reference from "Examples"Thomas Ackermann, Aug 25, 2013
  39. 12/13 Remove irrelevant reference from "Tying it all together"Thomas Ackermann, Aug 24, 2013
  40. Junio C HamanoAug 25, 2013
  41. Jon LoeligerAug 26, 2013
  42. 13/13 "git prune" is safe nowThomas Ackermann, Aug 24, 2013
  43. Junio C HamanoAug 25, 2013
  44. Philip OakleyAug 24, 2013

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.