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

Re: git branch: multiple --merged and --no-merged options?

From
Jeff King <peff@peff.net>
Date
Mar 22, 2013, 17:50 UTC
Message-ID
<20130322175034.GB29011@sigill.intra.peff.net>
In-Reply-To
<87fvzwmp23.fsf@59A2.org>
On Fri, Mar 15, 2013 at 02:38:12PM -0500, Jed Brown wrote:
> I find myself frequently running commands like this
> 
>   $ comm -12 <(git branch --no-merged master) <(git branch --merged next)
That's a reasonable thing to want to do.
> when checking for graduation candidates. Of course I first tried
> 
>   $ git branch --no-merged master --merged next

Yeah, sadly that does not work, as we use the same slot for the flag and store only one of the two (and we also allow only one "--merged" head, even though you could in theory want to know "merged to X, or merged to Y"). I do not think there is a reason we could handle both. I think we could even do it with a single traversal, but even with two traversals, doing both in-process will be faster (because we only have to pull the commits from disk once).

So I think it is something that ought to work, but it will need some code written. Patches welcome. ;)

-Peff
Previous: Jed BrownNext: Jed Brown
Message 2 of 4 in “git branch: multiple --merged and --no-merged options?”
  1. Jed BrownMar 15, 2013
  2. Jeff KingMar 22, 2013
  3. Jed BrownMar 23, 2013
  4. Jeff KingMar 23, 2013

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.