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

Re: [PATCH] cherry-pick: Add an option to prepend a string to the commit message

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 12, 2010, 06:18 UTC
Message-ID
<7vsk4sg4du.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20100612055831.GA2426@burratino>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 7 quoted lines
> Bobby Powers wrote:
>
>> This can be useful situations where you have a batch of commits to
>> cherry-pick and need to prefix each new commit message with similar
>> information
>
> Sounds reasonable.

It might be "usable in some limited context", but does not sound "reasonable" at all, sorry.

Especially since we will be getting "replay more than one commits in sequence", I would say it would make more sense to allow this kind of per-invocation (iow, command line option) commit transmonger a bit more flexibility, e.g. being a filter, or even a script that takes the original commit object name (so that it can consult git-vs-svn mapping in it if it wants to, for example).

Previous: Jonathan NiederNext: Jeff King
Message 3 of 9 in “cherry-pick: Add an option to prepend a string to the commit message”
  1. cherry-pick: Add an option to prepend a string to the commit messageBobby Powers, Jun 12, 2010
  2. Jonathan NiederJun 12, 2010
  3. Junio C HamanoJun 12, 2010
  4. Jeff KingJun 12, 2010
  5. Bobby PowersJun 12, 2010
  6. Jonathan NiederJun 12, 2010
  7. Jeff KingJun 12, 2010
  8. Junio C HamanoJun 14, 2010
  9. Junio C HamanoJun 14, 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.