On Wed, Mar 14, 2012 at 6:47 PM, Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> wrote: > Dmitry Potapov <dpotapov@xxxxxxxxx> writes: > >> Not of course. I said above non-fast forward push should not be used by >> beginners. > > Do you mean "beginners should not force non-fast forward push", or > "beginners should not use flow where push may be denied because of > non-fast forward"? Of course, the former. I have never said that the centralized workflow should never been used. I have only said that it is not scalable and lead to problems in larger projects. > If the second, this implies that beginners should never have a shared > repository, Well, you can set up a shared repository where everyone has their own namespaces to push. I don't say that that it is better than having one public repository per user, but it may be easier to setup... So it only implies that you cannot have a centralized workflow in this way. > either shared for one user and multiple machines, or shared > between developers? I am not sure that I understood this part. > If you mean that shared repositories are too complex for beginners, my > experience is exactly the opposite. It is not too complex but it is wrong for any more or less serious project. Git is flexible enough to cover different workflows, including some variant of a centralized workflow, but git was not designed with the centralized workflow in mind. So some trade-offs are different in it than in VCS that were designed primary (if not only) to be used with a centralized workflow. IMHO if you teach git then you should teach a distributed workflow, because it is the workflow where advantages of git is most obvious... Dmitry -- 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