> IOW, if the command was something like
> git filter-branch ...filter options... -- v1.0 master ...
> and v1.0 is an annotated tag, then it is reasonable to expect v1.0 to be
> deleted if the commit it points to goes away. But if the commit did not
> go away, but was rewritten, then it is equally reasonable to expect that
> the tag is also rewritten. But I don't think that we currently do the
When the commit doesn't go away, the tag is currently being rewritten properly.
> Therefore, IMO, a change that implements the former behavior should also
> implement the latter behavior.
The patch in my latest email does both. (yet lacks unit tests for now)
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html