On 05/24/2013 08:12 PM, Junio C Hamano wrote:
> Michael Haggerty writes:
>
>> Now assume a slightly more complicated situation, in which master has
>> been merged to feature branch at some point:
>>
>> o - 0 - 1 - 2 - 3 - 4← master
>> \ \
>> A - B - C - D ← branch
>>
[Junio, sorry for the dup; somehow I failed to CC the first version to
the mailing list.]
On 05/23/2013 07:20 PM, Junio C Hamano wrote:
> Michael Haggerty writes:
>
>> It seems to me that
>>
>> git rev-list --first-parent --ancestry-path A..B
>>
>> is well-defined and should list the commit
Michael Haggerty writes:
> It seems to me that
>
> git rev-list --first-parent --ancestry-path A..B
>
> is well-defined and should list the commits in the intersection between
>
> git rev-list --first-parent A..B
>
> and
>
> git rev-list--ancestry-pa
It seems to me that
git rev-list --first-parent --ancestry-path A..B
is well-defined and should list the commits in the intersection between
git rev-list --first-parent A..B
and
git rev-list--ancestry-path A..B
But in many cases the first command
4 matches
Mail list logo
