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

git log for a merged branch

From
SBStephen Bash <bash@genarts.com>
Date
Sep 8, 2010, 14:04 UTC
Message-ID
<14267801.230161.1283954674012.JavaMail.root@mail.hq.genarts.com>
In-Reply-To
<22744209.230141.1283954076245.JavaMail.root@mail.hq.genarts.com>
Hi everyone-
A coworker asked me a Git question yesterday that I can't answer, so I thought I'd pass it along:
Assume I have a release branch with bug fixes that is tagged at the end of the release cycle (let's call the tag tagFoo).  The release branch then gets merged back into mainline development (call the branch mainline), and the release branch is deleted.  If I want to see the commits (bug fixes) performed on the release branch, how do I do it?
I don't think
   git log mainline..tagFoo
works because all the commits of tagFoo are now reachable by mainline thanks to the merge.  Is there a simple way to express this concept?
Obviously in a pinch a simple
   git log tagFoo
will give you everything back to the beginning of time, but I think that's suboptimal...
To complicate things a bit more, in the real world there may be multiple merges from the release branch to mainline during the life of the release branch, so any solution that also deals with that would be outstanding (probably at the cost of additional complexity?)

Thanks, Stephen

Next: Tor Arntsen
Message 1 of 8 in “git log for a merged branch”
  1. Stephen BashSep 8, 2010
  2. Tor ArntsenSep 8, 2010
  3. Stephen BashSep 8, 2010
  4. Michele BallabioSep 8, 2010
  5. Stephen BashSep 13, 2010
  6. Santi BéjarSep 13, 2010
  7. Stephen BashSep 13, 2010
  8. Santi BéjarSep 13, 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.