On Fri, Dec 12, 2008 at 07:12:13PM +0000, David Howells wrote: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > > So I think that your document might do a good job scaring people away from > > Git. But I do not believe that your document, especially in the tone it > > is written, does a good job of helping Git newbies. > > Hmmm. So what would you suggest is a good way to write for GIT newbies? Is > it just that the overview should be canned or drastically simplified? The way I did it was to start with the directed acyclic graph of commits, explaining how branches fork the graph and merges join it. This was presented to people who know subversion, and so they immediately became aware that there are other ways to manage source code than in a linear r1 r2 r3 r4 r5. I described tags and branch heads briefly. Next up I described the things you'd do with git: add new commits, create a branch, merge a branch, rebase, tag, push and fetch and showed what that does with the dag of commits. Finally I showed the actual commands used to perform those actions. I didn't get into the object database structure at all (that was prepared in case I had extra time). I think a tutorial shouldn't be written in a way that polarises peoples' opinions or they come to regard git as a "necessary evil". If the audience is a person who knows nothing about git, that's hardly a "git hater" and I think the document starts off on the wrong foot as a result. Nick. -- 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
