tags vs branches in a repo

[Jan Hudec]

On Thu, May 11, 2006 at 22:59:55 +0200, Erik Bågfors wrote:
> If we go in a way that tags and named revisions, that means that they
> are not global for a repository.  Using branches as tags has the
> advantage that they are repository wide.

If we go in a way that tags are named revisions, that means that they *ARE*
global for a repository. They would be stored in a special knit and that
special knit would be in the repository. So there is no problem looking
there.

Besides, I'd actually think they should not be repository-wide, but
progeny-wide. But given that bzr repositories are not well suited to hold
multiple progenies anyway it may not be worth the trouble.

> For example, tag "release1" might not exist in a branch, because it
> was created before that tag was set, but is tags are branches, you
> know that you can always find it in "tags/release1" for example.

The tag 'release1' exists exactly where the tagged revision does. So if you
needed to go to master repository to fetch the tag-branch, you could fetch
the tag there as well.

> I'd like to be able to do both, I see real use for "named
> revisions"-tags as well as "tags as branches"..

IYou can always use branches as tags -- it simply works.

-- 
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- 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/20060511/d454d484/attachment.pgp