RE: Updated tags on repo are not updated when pull

From: Sebastien Tardif <sebastien_tardif@oxfordcorp.com>
Date: Apr 3, 2012, 12:00 UTC
Message-ID: <27353249354D994D8E42D75D75FBA6148967BE@OASBEVEXM01.oaifield.onasgn.com>
In-Reply-To: <27353249354D994D8E42D75D75FBA6148965A9@OASBEVEXM01.oaifield.onasgn.com>

Like almost everything else, if a local repo is not updated, many things like HEAD and branch may not point to the latest thing.

I agree that using branch is somehow a workaround, but it's still wrong that the tag is not updated by default when doing pull. Even if I find a long documentation about this behavior, it will still be wrong.

Let just admit git is still new, this use case is not original at all, it just show some outstanding issue with Git.

I'm used to work with SCM that that is server base, each extra step a developer need to do create issues and productivity lost. They just needed to do commit/update, but end-up forgetting "add" when creating new file.

Now with git beside still forgetting 'add" they forget to push. And now they will forget to do a extra "pull --tag".

Designed for failure.
________________________________________
From: pjweisberg@gmail.com [pjweisberg@gmail.com] on behalf of PJ Weisberg [pj@irregularexpressions.net]
Sent: Monday, April 02, 2012 7:29 PM
To: Sebastien Tardif
Cc: git@vger.kernel.org
Subject: Re: Updated tags on repo are not updated when pull

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.