Re: cvs tag: some slightly counterintuitive behaviour

[Derek Robert Price]

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

Andy Jones wrote:

>Now I come to make a release tag.  My expectation is that since cvs tag
requires a working directory then it will operate on that working
directory, tagging the files in it but *not* the files I have removed.


`cvs tag' is defined to tag the BASE revisions of the files in the
working directory and this is exactly the behavior you are describing.

I can see why you _might_ want to have cvs tag skip the removed files,
but this functionality extension cannot extend to modified and added
files since the revision to be tagged for a modified file wouldn't exist
in the repository and the entire archive file probably won't even exist
in the repository for added files, much less the revision to be tagged.

Therefore, I would argue that this sort of behavior is simply too much
to expect from CVS.

The work-around, and a pretty straight-forward one I should think, is to
commit your changes before tagging.

Derek

- --
                *8^)

Email: address@hidden

Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQFAYxfcLD1OTBfyMaQRAj7/AJ96FUwwvBWj0yh7i9nOu9qMUQxRFgCg1BC8
SL7oNcs2dOy4pS4IB9DtSUc=
=vpnJ
-----END PGP SIGNATURE-----