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

Re: Difficulty with getting an accurate changelog after cherry-picking and merging.

From
Alex Riesen <raa.lkml@gmail.com>
Date
Jul 22, 2008, 21:09 UTC
Message-ID
<20080722210924.GE5113@blimp.local>
In-Reply-To
<7dc909980807221338g707d6104ob8b1534cdf02a77a@mail.gmail.com>
Luuk Paulussen, Tue, Jul 22, 2008 22:38:19 +0200:
Show 5 quoted lines
> I'm trying to generate an accurate changelog of changes between 2 tags
> on a branch.  There is a merge between these 2 points which includes
> changes that were cherry-picked before the start point.  This causes
> the changelog to show these changes, despite them already existing
> before the start point of the log.

Cherry-picked commits are completely new commits and have no relation to the original commits whatsoever. Of course, they will be shown. It is literally a change made again, as if you typed it all in and committed.

Previous: Luuk PaulussenNext: Johannes Schindelin
Message 2 of 3 in “Difficulty with getting an accurate changelog after cherry-picking and merging.”
  1. Luuk PaulussenJul 22, 2008
  2. Alex RiesenJul 22, 2008
  3. Johannes SchindelinJul 22, 2008

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.