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

Re: UNS: Re: cherry-pick --message?

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Mar 28, 2017, 18:17 UTC
Message-ID
<20170328181709.GR31294@aiede.mtv.corp.google.com>
In-Reply-To
<20170328113055.GA5269@inner.h.apk.li>
Andreas Krey wrote:
> On Tue, 21 Mar 2017 13:33:35 +0000, Jeff King wrote:
Show 7 quoted lines
>> Probably "format-patch | sed | am -3" is your best bet if you want to
>> modify the patches in transit _and_ have the user just use normal git
>> tools.
>
> Except that 'git am' doesn't have --no-commit like cherry-pick does. :-(
> It's always something. (Perhaps I'm instead going to rewrite the commit
> before cherry-picking it.)

'git apply --index' can do that. I agree that it would be sensible for 'git am' to grow a --no-commit option to do that.

Thanks and hope that helps, Jonathan

Previous: Andreas Krey
Message 6 of 6 in “cherry-pick --message?”
  1. Andreas KreyMar 21, 2017
  2. Jeff KingMar 21, 2017
  3. Andreas KreyMar 21, 2017
  4. Jeff KingMar 21, 2017
  5. Andreas KreyMar 28, 2017
  6. Jonathan NiederMar 28, 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.