On Sat, 06 May 2006 13:09:03 -0700 Junio C Hamano <junkio@xxxxxxx> wrote: [...] > I think tutorial.txt is the right "your first experience with > git with walkthru" document, and the materials it gives, and the > order in which it introduces them, are very well thought out; > kudos to JBF. We might also want to show "git grep", but other > than that I do not think of anything that a new user might want > to use on the first day. It doesn't mention git log, show or status which are important for the first day. Also an example of git commit --amend would be a nice touch. Part of the problem people new to git are having arise by reading documentation in the wrong order and coming to the conclusion that git is an ugly beast. Also many people are still finding out-of- date information before anything else (eg. git isn't an scm only an object tracker). Part of this will be solved by having a useful and inviting web page (thanks Pasky!). But it would also help to rename core-tutorial.txt to something that doesn't sound inviting to newbies. Something along the line of core-internal-design.txt (or here-be-dragons.txt). Turning the main man page into more of a reference than a tutorial slash concepts page would be something worth doing too. Removing all of the plumbing commands from that page should at least be considered. [...] > Then reorganize the initial part core-tutorial.txt to match the > examples tutorial.txt gives, and demonstrate what is happening > under the hood. The tutorial says "git init-db" then "git > add". The core-tutorial would match that and explain what > happens when "git init-db" is run (creates .git/objects etc.) > and "git add" is run (populates the index). > There really seems to be a lot of room for another intermediate user level document between tutorial.txt and the current core-tutorial.txt. There are lots of concepts that can be explained without having to get into the low level design or tools of git. For example, a user could have long been productive with git before ever having to learn about read-tree/write-tree etc.. all those commands are more for porcelain writers and git guru/experts now. Sean - : 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