Hi,
On Thu, Jun 20, 2013 at 3:20 PM, Thomas Rast <[email protected]> wrote:
> Francis Moreau <[email protected]> writes:
>>
>> But I'm wondering if someone can see another solution more elegant ?
>
> I think there's a cute way. Suppose your arguments are of the form
Really nice !
>
> p1 p2 ... --not n1 n2 ...
>
> that is each pX is positive, and each nX is negative. Then as you
> observed, building the difference with master is easy: just add it to
> the negative args.
I didn't know that git-rev-parse could be used to transform any range
specification into that form (p1 p2 .. -not n1 n2..)
>
> Intersecting with master is harder, because you don't know what parts of
> it (if any) are in the range. But the --boundary option can help: these
> are the commits where the positive and negative ranges "first" met, and
> prevented the walk from continuing.
>
> So the part of master reachable from p1, p2, etc. is exactly the set of
> boundary commits of 'p1 p2 ... ^master'. And on top of that, excluding
> the parts reachable from the n's is easy. So you can do:
Really clever.
>
> positive=$(git rev-parse "$@" | grep -v '^\^')
> negative=$(git rev-parse "$@" | grep '^\^')
> boundary=$(git rev-list --boundary $positive ^master | sed -n 's/^-//p')
> # the intersection is
> git rev-list $boundary $negative
I think there's a minor issue here, when boundary is empty. Please
correct me if I'm wrong but I think it can only happen if positive is
simply master or a subset of master. In that case I think the solution
is just make boundary equal to positive:
# the intersection is
git rev-list ${boundary:-$positive} $negative
Now I'm going to see if that solution is faster than the initial one.
Great Thanks
--
Francis
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
