[merge] tags in repository

[John Arbash Meinel]

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

Aaron Bentley wrote:
> Jari Aalto wrote:
>>> Lukáa Lalinský <lalinsky at gmail.com> writes:
> 
> I've said it before, and I'll say it one last time:
> 
> tags should be per-project, not per-branch or per-repository.  We can
> work out the precise mechanism if we agree on that.
> 
> Aaron

I agree with you. The impedance mismatch is that we don't have "project"
 as one of our fundamental units.

Certainly there are ways to 'infer' project from other information
(overlapping ancestry, common tree root id, all in the same repository,
etc). In general, they are approximations, though. (overlapping ancestry
seems to be the most correct, but also has the worst performance
implications)

One way to be close would be to have per-repository tags, and only copy
a tag if you have the revision (or are getting the revision) it refers
to. It doesn't let you have 2 projects with the same tag, but it would
mean that you don't end up with tags for unrelated projects, just
because they existed in someone else's repository.

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

iD8DBQFFunZPJdeBCYSNAAMRAmrdAKCB9/QL9NTWH9cRC/YfMNRI4s27HwCgxPzy
VW2vriORCClyO1qGngYx3sk=
=EvBK
-----END PGP SIGNATURE-----