Comment 1 for bug 99137
Revision history for this message
| John A Meinel (jameinel) wrote Re: revert after merge leaves tags around | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Why?
Tags not a working tree operation. So 'revert' has no effect on them.
The local repository still has a copy of '<email address hidden>', so you could do
bzr merge -r revid:<email address hidden>
or equivalently
bzr merge -r tag:what
Supporting this would be tricky at best, because there are other ways to get tags. You can create a tag on an old revision (for example).
So if I tag revision -10 as "release-1.0". Which you already have (but I forgot to tag when I released).
And then you merge my tip because I've done more work. Do you want to not get that tag? Should "bzr revert" still remove the new tag (even though it is a tag on a revision in your current history)
If this is important to you, the best I can come up with is having merge track what tags are added (in a custom file) and then if you do "bzr revert" it will run "bzr tag --delete" for you.