> -----Original Message----- > From: git-owner@xxxxxxxxxxxxxxx > [mailto:git-owner@xxxxxxxxxxxxxxx] On Behalf Of Johannes Schindelin > Sent: Wednesday, July 16, 2008 5:28 PM > To: Avery Pennarun > Cc: Junio C Hamano; git@xxxxxxxxxxxxxxx > Subject: Re: Considering teaching plumbing to users harmful > > So can those people who have something to say about _my_ > subject of discussion please speak up? I think this issue > has not been discussed properly. > I've read this whole thread with great interest as I started learning and using git a few months ago. While I agree with you to a degree, there is a class of "newbies" to git who need more than just the basics that you outlined. For instance, I'm in the process of evaluating VCS's, and DVCS's in particular, to replace CVS at our workplace. Because of that, I need to get "up to speed" as fast as I can. I need to know about branches, how to browse history, merging, conflicts, etc. It is true, though, that I have a lot of experience doing these things already by virtue of the fact that I've used VCS's for over a decade and have been evaluating DVCS's for at least the past 3 years, so I have a bit of a head start on these things. To learn about these things, though, the sheer size of Git's vocabulary is huge compared to other DVCS's. That's a *good* thing, but it also makes it a bit harder to learn it all. It's just a fact of life. The first DVCS I learned was monotone. And I think what helped me the most in learning it is that it's syntax is very simple (you'd probably say limited compared to git, but that's neither here nor there, if you stick to your original list, git is as simple as monotone), it's repository format, the fact that each developer could keep one repository and create workspaces off of it was perfect for our workflows. What I think really helped with learning monotone is that they had a bunch of common workflows already documented and we could simply try them out. Maybe if Git had a few different workflows documented that might help. I know we have a "Git for SVN Users" workflow, but if you want to move beyond that, it might be good to have some of the more complex workflows documented. I think some people have hinted at that suggestion but that maybe it just hasn't been explicitly said. > Thanks. > Dscho > -- Cheers, Craig -- 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
