Re: Updated tags on repo are not updated when pull

From: PJ Weisberg <pj@irregularexpressions.net>
Date: Apr 2, 2012, 23:29 UTC
Message-ID: <CAJsNXTk8R0yjad0T9605v-CMMdCA+C0v3Rqt65h_k6MK88UD9g@mail.gmail.com>
In-Reply-To: <27353249354D994D8E42D75D75FBA614896543@OASBEVEXM01.oaifield.onasgn.com>

On Mon, Apr 2, 2012 at 12:16 PM, Sebastien Tardif <sebastien_tardif@oxfordcorp.com> wrote:

Show 7 quoted lines

> Default pull behavior does bring new tag that are hitting the revisions involved in the pull, in other words all tags that would point to log entries that are pulled.
>
> I have tag like: LATEST_UIT, LATEST_QA, LATEST_CONTINOUS_BUILD
>
> But with this incoherent behavior of not having the already pulled tag been updated when doing a pull, my developers end-up with misleading information in their log since their tags point to old pointer.
>
> Please fix.

There's a discussion in the git-tag man page about titled "On Re-tagging," the upshot of which is:

'Just admit you screwed up, and use a different name. Others have already seen one tag-name, and if you keep the same name, you may be in the situation that two people both have "version X", but they actually have different "X"'s. So just call it "X.1" and be done with it.'

You could use branches instead of tags for your 'latest X' things. A branch is basically a tag that moves.

-PJ

Gehm's Corollary to Clark's Law: Any technology distinguishable from magic is insufficiently advanced.