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

Re: [PATCH 7/8] Documentation/cherry-pick: describe passing more than one commit

From
Christian Couder <chriscool@tuxfamily.org>
Date
Jun 2, 2010, 05:57 UTC
Message-ID
<201006020757.15117.chriscool@tuxfamily.org>
In-Reply-To
<AANLkTikHODw5irE-84bkztWhUKgP8v1PG9zTW1Ea6WRs@mail.gmail.com>
On Tuesday 01 June 2010 11:29:32 Ramkumar Ramachandra wrote:
Show 23 quoted lines
> Hi,
> 
> Christian Couder <chriscool@tuxfamily.org> wrote:
> >  -n::
> >  --no-commit::
> > -       Usually the command automatically creates a commit.
> > -       This flag applies the change necessary to cherry-pick
> > -       the named commit to your working tree and the index,
> > -       but does not make the commit.  In addition, when this
> > -       option is used, your index does not have to match the
> > -       HEAD commit.  The cherry-pick is done against the
> > -       beginning state of your index.
> > +       Usually the command automatically creates some commits.  This
> > +       flag applies the change necessary to cherry-pick the named
> > +       commits to your working tree and the index, but does not make
> > +       the commits.  In addition, when this option is used, your
> > +       index does not have to match the HEAD commit.  The cherry-pick
> > +       is done against the beginning state of your index.
> >  +
> 
> Avoid re-wrapping the text so it's easy to see the changes that you
> have introduced in subsequent blames- you've just changed the word
> "commit" to "commits".
Ok, avoided the re-wrapping.
> > +Examples
> > +--------
> 
> Style nitpick: shouldn't the word "Examples" be in all-caps?

I had a quick look at Documentation/*.txt and found 22 files with "Examples" and 32 files with "EXAMPLES", so I changed to "EXAMPLES". But if you really care I suggest you to submit a patch to changes the 22 files that contains "EXAMPLES".

Thanks, Christian.

Previous: Ramkumar RamachandraNext: Jonathan Nieder
Message 21 of 30 in “implement cherry-picking many commits”
  1. 0/8 implement cherry-picking many commitsChristian Couder, May 31, 2010
  2. 1/8 revert: cleanup code for -x optionChristian Couder, May 31, 2010
  3. 2/8 revert: use run_command_v_opt() instead of execv_git_cmd()Christian Couder, May 31, 2010
  4. Jonathan NiederJun 1, 2010
  5. Christian CouderJun 1, 2010
  6. 3/8 revert: refactor code into a do_pick_commit() functionChristian Couder, May 31, 2010
  7. 4/8 revert: change help_msg() to take no argumentChristian Couder, May 31, 2010
  8. Jonathan NiederJun 1, 2010
  9. Jeff KingJun 1, 2010
  10. Jonathan NiederJun 1, 2010
  11. 5/8 revert: allow cherry-picking more than one commitChristian Couder, May 31, 2010
  12. Sverre RabbelierJun 1, 2010
  13. Jonathan NiederJun 1, 2010
  14. Junio C HamanoJun 2, 2010
  15. Christian CouderJun 3, 2010
  16. Jonathan NiederJun 1, 2010
  17. Christian CouderJun 2, 2010
  18. 6/8 revert: add tests to check cherry-picking many commitsChristian Couder, May 31, 2010
  19. 7/8 Documentation/cherry-pick: describe passing more than one commitChristian Couder, May 31, 2010
  20. Ramkumar RamachandraJun 1, 2010
  21. Christian CouderJun 2, 2010
  22. Jonathan NiederJun 1, 2010
  23. Ramkumar RamachandraJun 1, 2010
  24. Christian CouderJun 2, 2010
  25. Christian CouderJun 2, 2010
  26. Jonathan NiederJun 2, 2010
  27. Christian CouderJun 14, 2010
  28. 8/8 Documentation/revert: describe passing more than one commitChristian Couder, May 31, 2010
  29. Antriksh PanyJun 1, 2010
  30. Christian CouderJun 2, 2010

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.