I am brand new to git, and was pleased to find that the documentation explains concepts instead of only giving examples. I am confident that I can become much less of a newbie quickly.
One thing confused me -- the diagram on http://git-scm.com/book/en/Git-Basics-Recording-Changes-to-the-Repository shows that "add" moves something to an "unmodified" state. But it is clear from the text (and the add detailed documentation) that "add", whether of a new file or a modified file, moves a file to the "staged" state. I think the diagram might be changed to reflect this.
Based on my reading so far, I gather that, if I create a file in the working directory, it would start out as "untracked"; if I then use the "add" command on that file, it becomes "staged".
I might make an attempt at a new diagram, but I'm not confident enough that I am correct about this. Can someone confirm?
I am brand new to git, and was pleased to find that the documentation explains concepts instead of only giving examples. I am confident that I can become much less of a newbie quickly.
One thing confused me -- the diagram on http://git-scm.com/book/en/Git-Basics-Recording-Changes-to-the-Repository shows that "add" moves something to an "unmodified" state. But it is clear from the text (and the add detailed documentation) that "add", whether of a new file or a modified file, moves a file to the "staged" state. I think the diagram might be changed to reflect this.
Based on my reading so far, I gather that, if I create a file in the working directory, it would start out as "untracked"; if I then use the "add" command on that file, it becomes "staged".
I might make an attempt at a new diagram, but I'm not confident enough that I am correct about this. Can someone confirm?