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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
