From: Stefan Beller <stefanbeller@gmail.com>
To: "Wojciech Przybył" <przybylwojciech@gmail.com>, git@vger.kernel.org
Subject: Re: Potential bug in git client
Date: Wed, 11 Jun 2014 12:55:23 +0200 [thread overview]
Message-ID: <5398359B.6060907@gmail.com> (raw)
In-Reply-To: <CAKY5LXywixV3dWcCcVPTvyFrScJjLd8eoVs=RA1VRcrzUgtThQ@mail.gmail.com>
On 11.06.2014 12:21, Wojciech Przybył wrote:
> 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
next prev parent reply other threads:[~2014-06-11 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 10:21 Potential bug in git client Wojciech Przybył
2014-06-11 10:55 ` Stefan Beller [this message]
2014-06-11 11:09 ` Wojciech Przybył
2014-06-17 9:17 ` Michael Haggerty
2014-06-17 9:38 ` Wojciech Przybył
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5398359B.6060907@gmail.com \
--to=stefanbeller@gmail.com \
--cc=git@vger.kernel.org \
--cc=przybylwojciech@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.