On Wed, Apr 21, 2010 at 3:27 AM, Abhijit Menon-Sen <[email protected]> wrote: > Hi. > > I don't know if there are any git users here, but I wrote a concise > guide to sharing a single git repository among developers. It's meant > for small teams who are just adopting git and would like to get started > with a familiar setup. >
(this is not a comment on the contents of the tutorial) The problem with git is that the terminology and concepts are very unlike other version control systems (centralized or distributed). In my experience, at some point, many people coming to git after reading simplified HOWTOs and tutorials end up hitting a slightly complicated scenario and experience cognitive dissonance because they are trying to relate the problem to their (former) favorite version control system. And then they switch to Mercurial or something and bitch about Git on the web :) I advocate learning Git bottom-up[1], keeping aside concepts from SVN or CVS and understanding what commits,blobs, references and the index are. It would be make for more complicated reading, but would be better in the long run. Deepak [1] http://www.newartisans.com/2008/04/git-from-the-bottom-up.html
