On Thu, Jan 11, 2007 at 03:41:05PM -0800, Carl Worth wrote: > git commit -a > > Commit the working-tree content of all files known to git. > > git commit paths... > > Commit changes from the working-tree content of the specified > paths. > > git commit > > Commit changes from all content that has been staged with > "git stage". > [...] > I really like the simplicity of explanation that this model > provides. And I'd love to hear any feedback that anybody has about it. I think this is a very easy way of explaining it in the documentation. But what do you think 'git status' should say about changed files? Currently we make recommendations about how to stage the various files. It would certainly be simpler to recommend 'git commit -a' for changes, but that feels wrong. -Peff - 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