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

Re: [feature request] embed original commit info in cherry-pick

From
Jeff King <peff@peff.net>
Date
Feb 24, 2011, 19:12 UTC
Message-ID
<20110224191214.GC4318@sigill.intra.peff.net>
In-Reply-To
<4D66A3C9.7050001@genband.com>
On Thu, Feb 24, 2011 at 12:30:33PM -0600, Chris Friesen wrote:
Show 11 quoted lines
> 
> If I cherry-pick a  bugfix from a more recent version of a project, it
> would be useful to have an indication somewhere in the commit
> information of where it originally came from.
> 
> That way, if I then upgrade to a newer version of the software it
> becomes obvious that I don't need to worry about porting that commit
> forwards because it's already been handled upstream.
> 
> As it stands, it's not immediately obvious what was cherry-picked vs
> what was developed locally.
Have you tried cherry-pick -x?
-Peff
Previous: Chris FriesenNext: Chris Friesen
Message 2 of 3 in “[feature request] embed original commit info in cherry-pick”
  1. Chris FriesenFeb 24, 2011
  2. Jeff KingFeb 24, 2011
  3. Chris FriesenFeb 24, 2011

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.