[git-users] Re: Clone Shows Old Moved Files

2010-08-31 Thread Konstantin Khomoutov
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

[git-users] Re: Clone Shows Old Moved Files

2010-08-30 Thread Andrej Khitrov
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 -- You received this message because you are subscribed to the Google Groups Git for human beings group. To post to this group, send email

[git-users] Re: Clone Shows Old Moved Files

2010-08-30 Thread Andrej Khitrov
so git-mv implies to be used with git-commit if you want to save changes in git repository and not just in its staging area. -- 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.

Re: [git-users] Re: Clone Shows Old Moved Files

2010-08-30 Thread Gregg Leichtman
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. -= Gregg =- On 08/30/2010 04:18 AM, Andrej Khitrov

Re: [git-users] Re: Clone Shows Old Moved Files

2010-08-29 Thread Gregg Leichtman
I forgot to mention that I'm using Git 1.6.4.2 which appears to be the most current package for an OpenSUSE 11.2 install. You are doing exactly what I did, but in your example, I got a, b and c in the clone instead of just a and c. Maybe this is just an old bug. -= Gregg =- On

Re: [git-users] Re: Clone Shows Old Moved Files

2010-08-29 Thread Gregg Leichtman
I just upgraded to: g...@aragorn:~/gitClone/gitTest/src git --version git version 1.7.2.2 but I saw the same behavior. I tried it again and this time it worked as I expected. I believe that my error was that I did a git mv and then I immediately cloned. When I did a git mv FOLLOWED by a git