On Aug 30, 2:16 pm, Gregg Leichtman <gslac...@verizon.net> wrote:

>  From my CVS experience, I would expect the behavior that I have seen. I
> just forgot to do the commit and it didn't click that I missed the
> commit until I was told that it does work as I originally expected it
> should.
>> in fact git-mv (like git-add and git-rm) opperates just on working
>> directory and staging area (index) levels. It doesn't touch git
>> repository itself. So it

I tend to think Git only automatically records a commit when it's the
most sensible thing to do from the point of view of commit
"atomicity". Let me explain.
Take merging for example -- a merge which does not result in fast-
forward and does not fail due to conflicts is an atomic operation
since you hardly ever need to amend the commit resulting from a
successfull merge, and so the commit is done automatically (but you
can override this behaviour using --no-commit and introduce any
changes you want before committing).
Renaming a file, on the other hand, is quite an opposite kind of
operation: you might want to include several renames in your commit,
or you may wish to rename a file and then change it, and commit all
these changes at once. Or you might even want to modify a file, rename
it and then modify it again (using its new name).
Renaming a file is similar to editing a file in this regard: you just
modify a filesystem object.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to