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

Re: Question on for-each-ref and --contains

From
Øystein Walle <oystwa@gmail.com>
Date
Dec 23, 2014, 08:19 UTC
Message-ID
<loom.20141223T091605-427@post.gmane.org>
In-Reply-To
<CA++b5FaiKC2+U-Q_q7tBBjX2s+rLY6725H2ScUW26eOf-nmRjw@mail.gmail.com>
St. Blind <st.s.blind <at> gmail.com> writes:
Show 5 quoted lines
> 
> The > git-branch --contains and --merged are not very handy too,
> because the> output is not really flexible, and the --merged works
> on HEAD only.
> 
 
`git branch --merged foo` will list branches that are merged in the history
of 'foo'. And the equivalent is true for `--contains`. Not sure if that will
solve everything, though.
Øsse
Previous: St. BlindNext: Jeff King
Message 2 of 3 in “Question on for-each-ref and --contains”
  1. St. BlindDec 23, 2014
  2. Øystein WalleDec 23, 2014
  3. Jeff KingDec 23, 2014

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.