> From: Ed Pataky <ed.pat...@gmail.com>
> the downside of this seems to be that all the developers/contributors have
> to know how to merge correctly

Yeah, but that's true of any version control system that does not have
a centralized locking system to prevent two developers from changing a
single file simultaneously.

Or at least, *somebody* must be available to do necessary merging.
With Git, it's possible to have a developer create a new commit and
send it to the master repo but *not* have it become the "newest"
commit of the main line of development.  Then another developer can
download that commit and merge it into the main line.  With Git there
are always multiple ways of doing something.


You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to