El 20/2/2009, a las 19:13, Heiko Voigt escribió:
As far as I know all "sane" workflows involve topic branches, so
normally a developer will never commit directly on master but use
topic
branch instead and merge them into master once finished.
(Shudder... by that definition there must be a lot of insane people
out there!)
I think what constitutes a "sane" workflow depends very much on the
project in question, the number of developers, the collaboration model
etc.
I imagine there are plenty of developers (particularly those working
alone on small or private projects) for whom working directly on
"master" makes a lot of sense; after all, one of the great things
about distributed SCM is that what people do in their own private
repos is really up to them.
And what about "topics" that are really just a single commit? A one
line spelling fix, for example. Should that be done on a topic branch
and merged in too?
Horses for courses. In my own projects I work on master for some
things, and on topic branches for others, and I feel very sane.
Cheers,
Wincent
--
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
