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

Re: Tracking cherry picks

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Oct 20, 2011, 15:34 UTC
Message-ID
<CALkWK0k-0vtD6OUtqKzzG9_aqGm2jsDY1k=xCR43TssvnHyLPg@mail.gmail.com>
In-Reply-To
<37162B20-4758-433E-B11E-CE4B7FF27FBA@gmail.com>
Hi,
Kirill Likhodedov writes:
Show 6 quoted lines
> 20.10.2011, в 18:21, Phillip Susi:
>>  Why doesn't git-cherrypick record the original SHA1 it was picked from in the commit?
>
> It does if you specify "-x" option to cherry-pick
> See the man for git-cherry-pick:
> [...]

Right. As an interesting historical note, git has been omitting the original object name by default when cherry-picking/ reverting since abd6970a (cherry-pick: make -r the default, 2006-10-05).

-- Ram
Previous: Kirill LikhodedovNext: Jonathan Nieder
Message 3 of 4 in “Tracking cherry picks”
  1. Phillip SusiOct 20, 2011
  2. Kirill LikhodedovOct 20, 2011
  3. Ramkumar RamachandraOct 20, 2011
  4. Jonathan NiederOct 21, 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.