how to fix the broken tagging system?

[Ronny Pfannschmidt]

On Mo, 2008-09-29 at 00:14 +0200, Dirkjan Ochtman wrote:
> Ronny Pfannschmidt wrote:
> > 1. Tags don't propagate with the tagged revision.
> > 
> > It's really not fun to push a tag just to see its not there in the
> > remote repository.
> 
> I have proposed fixing this by disallowing tagging changesets that are 
> not in the ancestry for the tagging changeset. mpm was a little on the 
> fence about it, but I still think this is a good UI-level feature which 
> helps prevent this kind of problem.

Sounds tricky, it would require special cases to chose child revs of
tagged revs for pushing.

> 
> > 2. Tags can change without further notice
> > 
> > Its really no fun to pull in changes, and get existing tags changed that
> > way - no pull op should be able to alter tags without asking me first.
> 
> It seems to me you are contradicting yourself here:
> 
>  > No, i belive creating a history for metadata about the history is the
>  > wrong way.
> 
> So on the one hand, you want to get notice of changed tags, and on the 
> other hand, you believe the metadata about history should not be 
> versioned itself?
well, complaining about remote tags that differ from local ones shouldn't be much of an issue

git simply ignores all changes to remote tags after it first got them 
(the only way to fix stupid is to make everyone explicitly remove the old one and fetch the new one)

Regards Ronny