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

Re: finding unmerged branches

From
Joey Hess <joey@kitenet.net>
Date
Aug 28, 2009, 00:44 UTC
Message-ID
<20090828004450.GA20964@gnu.kitenet.net>
In-Reply-To
<20090827223504.GA18307@atjola.homenet>
Björn Steinbrink wrote:
Show 10 quoted lines
> Hm, not sure if I'd call it "better", but probably at least a bit
> faster. You could create a "fake" merge to combine all the branches.
> 
> git branch -r --no-merged $(
>   : | git commit-tree HEAD^{tree} $(
>     git for-each-ref --format='-p %(refname)' \
>       refs/heads/ \
>       refs/remotes/origin
>     )
>   )

That does run fast. Has some warnings about duplicate parents. The gitk method seems more useful.

-- 
see shy jo
Previous: Junio C HamanoNext: Joey Hess
Message 6 of 7 in “finding unmerged branches”
  1. Joey HessAug 27, 2009
  2. Avery PennarunAug 27, 2009
  3. Joey HessAug 28, 2009
  4. Björn SteinbrinkAug 27, 2009
  5. Junio C HamanoAug 27, 2009
  6. Joey HessAug 28, 2009
  7. Joey HessAug 28, 2009

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.