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

Re: git cherry-pick feature request

From
Junio C Hamano <junkio@cox.net>
Date
Aug 23, 2006, 09:51 UTC
Message-ID
<7vfyfnixv5.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<17643.62896.396783.890223@cargo.ozlabs.ibm.com>
Paul Mackerras <paulus@samba.org> writes:
> Could I have a flag to git cherry-pick (-q for quiet, maybe) that
> tells it not to print anything if the command succeeds?  Could I also
> have a flag that tells it to clean up if the merge fails and leave the
> tree in its previous state?
Quiet sounds sane.

Reverting to its "previous state" I am not quite sure if it is worth making it an option and run it as part of cherry-pick.

Previous: Paul MackerrasNext: Paul Mackerras
Message 2 of 7 in “git cherry-pick feature request”
  1. Paul MackerrasAug 23, 2006
  2. Junio C HamanoAug 23, 2006
  3. Paul MackerrasAug 23, 2006
  4. Jeff KingAug 23, 2006
  5. Junio C HamanoAug 24, 2006
  6. Junio C HamanoAug 24, 2006
  7. Paul MackerrasAug 24, 2006

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.