tags in bzr

Martin Pool mbp at sourcefrog.net
Fri May 13 00:09:23 BST 2005


On 12 May 2005, Erik B?gfors <zindar at gmail.com> wrote:

> I want a tag to be a named revision. Reading trough tagging.txt, the
> "tags within a branch" is pretty much what I want. So... I don't like
> reading the "(This is probably "crack"; I don't think we'll do
> this.)"-line.

> Basically if I do "bzr log" I want to see the following
> 
> ......
> 
> ------------------------------------------------------------
> revno: 280
> tag: 0.0.4pre
> committer: Martin Pool <mbp at sourcefrog.net>
> timestamp: Fri 2005-04-22 11:40:26 +1000
> message:
>   Prepare for 0.0.4 release
> ------------------------------------------------------------

That looks good.

> and then I want to be able to do 
> bzr get -r 0.0.4pre http://.......        or maybe it's better to do:
> bzr get --tag 0.0.4pre http://......
> 
> as well as
> bzr merge -r 0.0.4pre http://.... (or, however the final syntax will be)
> 
> 
> This is basically how darcs works also.
> 
> So.. what do you all think? If you want it the same way as I do, I
> might be willing to implement it even.  It's quite an important
> feature for us.

I think we should do this, despite my earlier reservations.  What
you've listed here should be reasonably simple.

There are just a few open issues:

- What names are allowed for tags?  I am inclined to say that, like
  programming language identifiers, they can't start with a digit so
  that we can distinguish them from revision numbers and pass both to -r.

- Should tags propagate across merges?  I think yes; people may have
  to adopt some conventions to avoid getting too many conflicts, such
  as starting personal-use tags with their username.

- Are tags themselves versioned, and if so how?  The simplest thing is
  to say, no, they're not versioned.  Perhaps placing a tag should
  create a new revision, but that has the strange side-effect that if
  you check out a tag, you can no longer see the tag because it
  doesn't exist yet.

I don't think any of these need to prevent doing the core feature though.

-- 
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050513/1014b01a/attachment.pgp 


More information about the bazaar mailing list