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

On Fri, Mar 22, 2013 at 09:46:42PM -0500, Jed Brown wrote: On Fri, Mar 15, 2013 at 02:38:12PM -0500, Jed Brown wrote: $ 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

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

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

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

Jeff King p...@peff.net writes: On Fri, Mar 15, 2013 at 02:38:12PM -0500, Jed Brown wrote: $ 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

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

I find myself frequently running commands like this $ comm -12 (git branch --no-merged master) (git branch --merged next) when checking for graduation candidates. Of course I first tried $ git branch --no-merged master --merged next but this is equivalent to $ git branch --merged next