on moving tags

[Aaron Bentley]

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

John Yates wrote:

| I find "snapshot name" better captures the notion of
| a tag and its intended role.  Similarly I am partial to the "line of
| descent" phrase as opposed to "branch".

In bzr parlance, 'revision' is the term for an addressable snapshot.  So
'revision tag' (to mingle Arch and CVS terminology!) would suit me fine.
~ 'Tag' connotes something added to an object to describe it, while
'name' connotes something permanent and integral, so I think tag is the
better term (and less confusable with the permanent 'revision id').

I agree that there is an unfortunate overlap between filesystem
heirarchy terminology and geneological terminology.  As a result, we
have 'branches' and inside those branches, we have multiple 'revision
trees'.

More precise terms like 'line of descent' could be listed as alternates,
but we must use existing jargon where the meaning is reasonably similar.

| At the very least I hope that bzr eschews within its CLI CVS's
| conflation
| of "branch tags" and "revision tags".

The interesting thing is, you can represent a revision tag as a locked
branch.  So how much conflation is that, really?

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

iD8DBQFCihOI0F+nu1YWqI0RAminAJ9u4UnXmUuLnSqngcDk5xrgq2f6RgCfYtte
M8Ve2QhwKpN2P1rq8KSthu4=
=ndNC
-----END PGP SIGNATURE-----