[merge] tags in repository

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nicholas Allen wrote:
> 
>> Good for you. Not so good for someone who has put several projects to
>> same repository. When that someone pushes or someone other pulls from
>> him/her, all the other project tags go too.   
> I agree too. Currently, in bzr you could make your home directory a
> shared repository so that all projects are stored in the same repo and
> you don't have to keep setting up new ones for new projects. I don't
> work like this but I can see how some people might like to. If the tags
> are mapped across the repository then this would cause lots of problems
> wouldn't it? Nothing stops a developer doing this and then they will get
> all sorts of problems with the tags if they are not unique across all
> projects. I would also like to give a tag like 0.1 without having to
> specify my-project-0.1.
> 
> I would like versioned tags that are part of a branch and not repository.
> 
> Nick

There is a big problem with 'versioned tags that are part of a branch',
in that if you update a tag to something newer, you can't see that in
your branch.

Well, it sort of depends on how tags are implemented. If you do
'committed' tags like 'hg' does, then if you 'bzr revert -r OLD', your
tag dictionary is also reverted, and you see only old tags (and don't
even see new tags).

You could alternatively make a per-branch tag list, but allow that to be
updated separately from commited revisions.

You still get into problems with having an old branch and wanting to
update to a specific tag from another branch without having to pull from
that branch.

So there are some possibilities, but it is a lot of tradeoffs where you
lose some very nice functionality because you want different functionality.

I think Martins' implementation is a very good start. And we can look
into how to refine some of the edges. But these sorts of disagreements
are why bzr doesn't have tags yet.

No implementation can satisfy everyone all the time, so we need
something to satisfy 95% of the use cases.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFuOTWJdeBCYSNAAMRAkBfAKCgoCmmaAzP+2+BPjz4wldCajZIogCfUdlC
fZ/reE+iAZwPrx+DWe66GnY=
=88Ru
-----END PGP SIGNATURE-----