[PLUGIN] Updated tags plugin

[Aaron Bentley]

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

John Arbash Meinel wrote:
> That specific bug is because only things which bzr knows about are ever
> carried across by branch. 'bzr branch' regenerates everything.
> I think we probably need to add a place for plugins to put hooks so that
> their metadata can get copied across. Until now, we didn't have plugins
> which stored stuff inside .bzr.

Err, push, rpush, rpull?

> And then their are the failure scenarios. Of "I don't know what to do
> with 'foo', do I fail to run, do I ignore it, do I copy it, etc".

It is *very* hard to selectively update data without understanding its
semantics.  In the case of tags, you should combine them, but what do
you do if the same tag name is already locally defined?

> I would probably start with #1, because whatever we do, we need a
> run-time custom behavior which plugins can define.

Yes, that makes sense to me, if we want to support this.

> [Tags] should be meta-information about revisions, not tied
> underneath them. Though it did solve the merge issues.)

Yes, I tend to agree on both points.

Aaron

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

iD8DBQFDnuFr0F+nu1YWqI0RAog8AJ9Kgx1UoB+azid0BqLM/vYzSV7LWwCfUEz+
s0mudcD7TodlrJ/gP6z3R0U=
=P8eY
-----END PGP SIGNATURE-----