Santi,
Thanks for you reply.
> I think your definition is not well defined. A, B and C are just
> branches of you project, technically they are equivalent. Maybe you
Right. Yet I want to know from which branch a branch as been started.
You need this to get the proper merge-base for example:
$ git merge-base C A
1
$ git merge-base B C
2
$ git merge-base B A
1
I always know on which topic branch I'm but, as shown above, depending on the
parent branch passed to merge-base you do not get the same branch-point. This
is fine.
So, when I'm in a topic branch I want to find the name of the parent
branch. The one given
when creating the branch:
$ git branch B C
A "stupid" solution whould be to iterate over all branches. Looking
for the merge-base and
at the end output the branch having the youngest merge-base. I'm
looking for something
more efficient...
> are thinking that the common commits of, say A and B, really belongs
> to A, but this is not the case they belong to both branches. In git a
> branch is really just a pointer to a commit and by extension the
> history, it is not a series of commits.
>
> 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.
Don't see this as a counter-example as it is exactly my example.
Did I missed something?
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
