Updated tags support

John A Meinel john at arbash-meinel.com
Fri Dec 30 21:20:12 GMT 2005


Jan Hudec wrote:
> On Fri, Dec 30, 2005 at 15:12:13 -0600, John A Meinel wrote:
>> Jan Hudec wrote:
>>> On Thu, Dec 29, 2005 at 13:03:33 -0600, 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`
>>> AFAICT bzr does not support checking out different revision than the
>>> current head, so there is no ambiguity.
>>>
>>>> and `bzr settag` and family, just make me twitch.  I'm slowly moving
>>>> stuff into bzr instead of into tla for a _reason_!
>> I believe Matthew was referring to the behavior of Niemeyer's tag
>> branch, where "bzr set-tag FOO" sets a tag such that it gets the
>> revision id of the next commit.
> 
> Well, that's outright bogus. Didn't realize this part of the question.
> 
>> If we separate tags from the commit logic, I don't think this is necessary.
> 
> I agree with separating them. I don't want to think ahead of commit that
> I want to give it a name.
> 

Well, you could always set it after the fact, but it would require
*another* commit.

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/accc999f/attachment.pgp 


More information about the bazaar mailing list