Le 22/10/2009 10:27, Thomas Rast a écrit :
I think this not only changes the model of branches, but also commits,
to some extent. Currently, commit have no intrinsic branch
membership; if you say
git branch foo bar
you cannot distinguish whether the commits on 'bar' were created on
'foo' or on 'bar'. (By git's means; of course the decision would
favour 'master' if I had used that instead.)
I have been looking for a way to know that. I've even post a question
about this on this mailing-list long time ago IIRC.
To me there is case where it is important to know which are the commits
done on a topic branch for example. When working on multiple topic it is
difficult to remember which commits have been done on this specific
branch. This is needed to rebase onto:
$ git rebase --onto somebranch <topic_base> <topic_head>
A common idiom, but one as to think hard (& right) to properly get the
topic_base today.
Just my 2 cents!
Pascal.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net - http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B
--
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