git pull regression?
- From
- Carlos R. Mafra <crmafra2@gmail.com>
- Date
- Nov 4, 2008, 22:27 UTC
- Message-ID
- <20081104222749.GA9296@localhost.aei.mpg.de>
Hi,
I tested git v1.6.0.3 today and noticed that git pull is behaving strangely, compared to what I was used to with v1.5.6.3
It no longer tells me "Already up-to-date." when it used to, now it simply says nothing.
And when I pulled Linus tree for the kernel this morning it downloaded the new commits but git didn't show the diffstat.
Furthermore, it kept saying to me "Your branch is behind 'origin/master' by 31 commits, and can be fast-forwarded" and git log was not showing the new commits.
At first I thought I had made some mistake with my repo, but I searched the mailing list and there was a similar case which was "fixed" after using 'git status' followed by another 'git pull'. But in my case it did not help.
So I went back to v1.5.6.3 and everything was back to normal.
After that I made some tests, and v1.6.0 was good and v1.6.0.1 was bad, but I didn't bisect it further.
It looks like a regression to me. I can finish the bisection if people in the list say that I am not making a mistake somewhere :-)