Greetings, I just did "git-clone git://git.kernel.org/pub/scm/git/git.git". git-pull in the resulting repository gives "Already up-to-date." and "git-pull --tags" does the same. Just what I'd expect. Before I did that, I had an old (several months) git.git repository laying on the hard drive and I updated it with "git pull". It complained something tag related and I tried again with "git pull --tags". Now I'm in a situation where "git-pull --tags" gives "No changes." but plain "git-pull" gives me this: ------------------------------------------------------------------- remote: Generating pack... remote: Done counting 293 objects. remote: Result has 214 objects. remote: Deltifying 214 objects. remote: 14/214) done14) done Unpacking 214 objects remote: Total 214, written 214 (delta 156), reused 181 (delta 123) 100% (214/214) done error: no such remote ref refs/heads/jc/bind error: no such remote ref refs/heads/jc/bind-2 error: no such remote ref refs/heads/gb/diffdelta * refs/heads/pu: not updating to non-fast forward branch 'pu' of git://git.kernel.org/pub/scm/git/git old...new: 0c9951a...f959571 Already up-to-date. ------------------------------------------------------------------- If I run either git-pull or "git-pull --tags" again, I get the same results. Since updating a freshly cloned repository doesn't result to such an odd behaviour, I assume this old repository is broken somehow. If someone wants to inspect it, I can make it available via web. I'm using git 1.4.4.3 on Debian GNU/Linux. -- Hannu - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html