Santi,
> Maybe if you explain why you want it (a use case) instead of just this
> specific problem...
To know the proper merge base to display all commits done on a specific
topic branch.
>>> Just a counterexample, just rearranging you graph:
>>>
>>> o---B
>>> /
>>> o---2---o---o---o---C
>>> /
>>> ---o---1---o---o---o---A
>>>
>>> From you description: For B I would get C and for C I would get A.
>
> Please, if you quote text do not edit it (the 1 and the 2 in this case).
Well I've just added 1 and 2, nothing changed in the semantic!
> Yes. Compare your sentence and mine:
>
> For B I want to get A and for C I want to get B.
> For B I would get C and for C I would get A.
>
> So for B you get A while I get C, and the equivalent for C.
Ok, that's expected since you have renamed B to C and C to B.
My tree was:
o---o---o---C
/
o---o---o---B
/
---o---o---o---o---o---A
Your's was:
o---B
/
o---o---o---o---o---C
/
---o---o---o---o---o---A
So when I said:
For B I want to get A and for C I want to get B.
It is equivalent to your (just rename B and C).:
For B I would get C and for C I would get A.
Frankly I do not see your point... That's maybe the cause of the
problem I'm having....
Pascal.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
