Re: Updated tags on repo are not updated when pull

[Marc Branchaud <marcnarc@xiplink.com>]

On 12-04-03 08:00 AM, Sebastien Tardif wrote:
> Like almost everything else, if a local repo is not updated, many
> things like HEAD and branch may not point to the latest thing.

You need to wrap your head around the concept that git keeps your local 
repository's branches separate from any remote repositories'.  Even if 
my local repository has a branch "foo" and the remote also has a branch 
"foo", git stores these in separate namespaces.

> 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.

Well, that's debatable and depends on how you're using git.  Other 
people's processes *want* the tags to remain unchanged.

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

And indeed has been discussed at length.  The latest proposal was about 
letting tags have local and remote namespaces and to have "git fetch" 
automatically move remote tags, just like remote branches:

http://thread.gmane.org/gmane.comp.version-control.git/165799/focus=166118

		M.