Re: Potential bug in git client

From: Stefan Beller <stefanbeller@gmail.com>
Date: Jun 11, 2014, 10:55 UTC
Message-ID: <5398359B.6060907@gmail.com>
In-Reply-To: <CAKY5LXywixV3dWcCcVPTvyFrScJjLd8eoVs=RA1VRcrzUgtThQ@mail.gmail.com>

On 11.06.2014 12:21, Wojciech Przybył wrote:

Show 28 quoted lines

> Hi All
> 
> When I was tagging, I think I might have discovered a git client bug.
> 
> HOW TO REPRODUCE:
> - Clone a repo into 2 separate directories. Presume there is a tag
> "v0.1" already in there and it is set on say 10 commits ago.
> 
> - In first directory change the tag to a different place and push it
> to the server:
> git tag -d v0.1
> git tag v0.1
> git push --tags origin master
> 
> - In second directory try to update the tag...
> git pull --all --tags
> git fetch -all --tags
> THIS DOES NOT WORK, tag is still at old place, but it says "Already up-to-date".
> 
> - I noticed when I use:
> git fetch --tags
> it works fine and updates the position of the tag, or if I remove tag
> from local git manually (rm .git/refs/tags/v0.1) and update again.
> 
> Is it a bug or I am doing something wrong? I use git version 1.7.9.5.
> 
> Cheers
> Wojciech

Tags are intended to not change without the user knowing. To gain more understanding on that, maybe read the man page of git tag (see the discussion on retagging) https://github.com/gitster/git/blob/master/Documentation/git-tag.txt#L166