On Aug 30, 2:16 pm, Gregg Leichtman 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 (lik
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 wrot
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.
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
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
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 08/29/20
On Aug 30, 1:54 am, gsl1 wrote:
> I created a local git repository and committed a directory of files to
> it successfully. I then altered one of the files and committed it
> again. Then I did a git mv on the same file to a new file. All worked
> as expected. Next I made a new local repository of
