On 03/05/2011 03:29 PM, Wols Lists wrote:
On 05/03/11 09:30, Steve Romanow wrote:
Git- I personally think git is best for very large workgroups working
on a single large codebase (i.e. an os kernel). It is primarily geared
to people comfortable in the shell. It does _not_ have good win32
support so it is a non-starter for me.
Mmmm.
I take your point about it being a cli program, not a gui.
But why is it best "for large workgroups"? True, it makes merging stuff
into a single central repository easy, but most of its features are
aimed at the "lone" developer. It's just that they're the same features
that are needed by a group.
If you're trying to work on several things at once, it makes your life
easy. Where's the difference between one developer multi-tasking, and
multiple developers co-operating?
Cheers,
Wol
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
I stand corrected. I have not used git so I should prob reserve any
judgement.
I guess the only thing I have experienced with it is it seems more
complicated than both hg and bzr. I like the single hg command with
many subcommands and the plugin structure of bzr and hg.
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
