Fossil SCM
fossil tag cancel has no effect?
f273b440c38eb84…
· opened 17 years, 3 months ago
- Type
- Code_Defect
- Priority
- Immediate
- Severity
- Important
- Resolution
- Open
- Subsystem
- —
- Created
- Dec. 17, 2008 10:13 p.m.
In the TDBC repository at http://kbk.is-a-geek.net:2301/, I made some last minute changes, and wanted to move the release tag '1.0b1' to the newly-committed version. I did
fossil tag cancel 1.0b1 cdc04f749733684d55cd9eb1f440e6d4e47b03f9
followed by
fossil tag add 1.0b1 fbd0e6a2758844dfe651e0f6e78c9e527ba860a5
But now when I do
fossil tag find 1.0b1
I see both versions.
Did I do something amiss, or am I misunderstanding something? My objective is to arrange things so that '1.0b1' can be used as a tag to check out the released version while development proceeds. (I'm not looking to branch it yet, merely to tag and bag the release)
eric added on 2008-12-17 22:39:08:
I think it's just the listings (the web shows both too), but if you do a
fossil update 1.0b1
after the cancel and before the add, you get "not a valid object name", as expected.
eric added on 2008-12-20 11:39:25:
Fixed in [7c281b629ac5c6a91b2b8143fe48a5714f54e0df]