Re: [PATCH] make 'git add' a first class user friendly interface to the index

[Nicolas Pitre <nico@cam.org>]

On Sat, 2 Dec 2006, Alan Chandler wrote:

> So I am with you that we need to effective teach
> 
> git add <filename>   #add content of filename to the SCM
> #edit <filename>
> git commit -a		#commit current state of all tracked content
> 
> first, and then move on to teach selective commiting

I think that's pretty much what my patch to the tutorial does.

The tutorial talks about:

	1) git init-db

	2) git add .

	3) git commit

	4) modifying some files then git diff

	5) git commit file1 file2, or git commit -a

Then goes the discussion about what git add does and why.  It is quite 
early in the tutorial and making it earlier would be a bit premature.  
Let's have the user make his first simple commit while blindly 
following the instructions before going with the 
actual usage model.  At that point,since we just mentioned "git commit 
file1 file2" or "git commit -a" will the user be in the proper mindset 
to wonder why not using plain "git commit"... and incidentally the whole 
explanation is there to follow immediately.

I'm reworking my patch with suggestions that have been posted so let's 
hope it'll be even clearer.