Problems with deleting tags?

Richard Wilbur richard.wilbur at
Sat Apr 16 15:33:27 UTC 2016

On Sat, Apr 16, 2016 at 5:59 AM, Vincent Ladeuil <v.ladeuil+lp at> wrote:
>>>>>> Joshua Judson Rosen <rozzin at> writes:
>     > Basically, the issue you're having is related to the fact that
>     > tags in Bazaar are just not, themselves, revision-controlled;
> This is the crux indeed, they still aren't version controlled and
> --overwrite-tags is a way to fix the edge cases.
> <snip/>
>     > i.e.: once a release tag is published/propagated to a scope where
>     > it becomes difficult to take it back, you deal with the "oh, no, I
>     > didn't mean to release _that_!" situation by _doing an additional
>     > point release_.
> And this is indeed the best available way to deal with the issue: create
> a new tag whose semantic override the previous one and then /forget/ the
> previous one ever existed.
> But sometimes you can't do that which is, I think ckalisiak issue.
>     > It's basically the same situation as with rebasing or
>     > uncommitting: being able to create not just *revision history* but
>     > *revisionist history* is a great tool... right up to the point
>     > just before you publish, but not beyond that point.
> Yup, well articulated.
> <snip/>
>     > Even if revision control means never having to say you're sorry,
>     > it does sometimes mean having to admit you were wrong :)
> And to close the loop about tags not being version controlled, this
> means that bzr doesn't offer a way to express changes for a tag in a way
> that can be properly distributed.

Do we improve things if we make tags version controlled?

My understanding of tags is probably incomplete but it at least
connotes creating a name for a snapshot of version information.  What
would it mean to make tags version controlled?  Would you be able to
revise the version information associated with a tag and have a
history for the version information associated with each tag?


More information about the bazaar mailing list