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

Re: git log for a merged branch

From
SBStephen Bash <bash@genarts.com>
Date
Sep 13, 2010, 14:13 UTC
Message-ID
<15224422.248536.1284387218322.JavaMail.root@mail.hq.genarts.com>
In-Reply-To
<AANLkTikbnoR_=x1_Aq4jh1BuMarEMxXkY=iX0iOjdgyt@mail.gmail.com>
----- Original Message -----
Show 13 quoted lines
> From: "Santi Béjar" <santi@agolina.net>
> To: "Stephen Bash" <bash@genarts.com>
> Cc: "Michele Ballabio" <barra_cuda@katamail.com>, "Git Mailing List" <git@vger.kernel.org>
> Sent: Monday, September 13, 2010 10:00:18 AM
> Subject: Re: git log for a merged branch
> 
> If there is more than one merge-base you´ll have to use:
> 
> git log mergecmt^2 --not $(git merge-base mergecmt^1 mergecmt^2)
> 
> and you may use this shorter form:
> 
> git log mergecmt^2 --not $(git merge-base mergecmt^@)
That's surprisingly compact...  Impressive.
Slightly changing the topic, we normally tag the release branch, then merge, then delete the branch.  Is there a simple way to determine mergemt from the release tag?

Thanks, Stephen

Previous: Santi BéjarNext: Santi Béjar
Message 7 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.