Updated tags support

[John A Meinel]

Matthew D. Fuller wrote:
> On Thu, Dec 29, 2005 at 10:11:56AM -0800 I heard the voice of
> Robey Pointer, and lo! it spake thus:
>> I've been trying to stay out of this one, but I can't resist any
>> more.
>>
>> This all seems ridiculously complex.  Commit a tag? What? :)  Could
>> we simplify this down?
> 
> That's my feeling.
> 
> % bzr tag -r78 FOO
> % bzr tag --delete FOO
> % bzr tag --move -r79 FOO
> % bzr tag --list
> 
> Those all seem pretty self explanatory.  The only obvious ambiguity is
> whether "bzr tag FOO" would tag the head of the tree or the currently
> checked-out rev.  Commiting tags, or `bzr showtag` and `bzr movetag`
> and `bzr settag` and family, just make me twitch.  I'm slowly moving
> stuff into bzr instead of into tla for a _reason_!
> 
> 

I think under this system 'bzr tag FOO' should tag the last committed
revision. That makes it nice and orthogonal to everything else. (For
example, you could create a tag on a branch which doesn't have a working
tree).

I would also like to see a way to specify a branch other than the local
one. So that you can create tags in a future repository. So I would tend
to make the interface:

bzr tag -rREV TAGNAME location?
I don't know if you need --move, perhaps we should have it as a safety
measure. Though we already have --force. So we could say

bzr tag -rREV mytag
Fails if mytag already exists, and will update the tag if --force is used.

We could also have either:
bzr tags
Which provides the list of all tags. But that would be another command,
rather than just using --list.

I wrote up the system I like on the wiki.
http://bazaar.canonical.com/BzrTagging

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051230/07fb3a4e/attachment.pgp