Re: able to remove tagged files

[Mark D. Baushke]

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

Jim.Hyslop <address@hidden> writes:

> Mark D. Baushke wrote:
> > It is possible to remove tagged files from the current branch or the
> > trunk because a checkout using the tag will still checkout the tagged
> > version of the file with no problems.
> > 
> >   cvs checkout myproj
> >   cd myproj
> >   cvs tag my-release-1-0
> >   : assume that there is a foo.c version 1.12 here
> >   cvs remove foo.c
> >   cvs commit foo.c
> >   cvs log foo.c
> >   : you will see the output about version 1.13 being a 'dead' version
> There's a step you left out - before the remove, 'cvs update -r
> my-release-1-0'. This gives much more, er, interesting results:

Actually, I didn't go down that path as I was not sure that was the
complaint. Sure 'cvs rm file' when you have a checked out version tag
will remove the tag from the file the same as 'cvs tag -d' does.

As Larry has mentioned, this is something that has been discussed in the
past as a possible missfeature. No one has thought it was bad enough to
patch yet.

        -- Mark

> 
> E:\cvs\cvs-test\jhyslop\test_tags>echo hello>test.txt
> 
> E:\cvs\cvs-test\jhyslop\test_tags>cvs add test.txt
> cvs server: use 'cvs commit' to add this file permanently
> 
> E:\cvs\cvs-test\jhyslop\test_tags>cvs ci -m"Adding file" test.txt
> RCS file: /cvs/cvs-test/jhyslop/test_tags/test.txt,v
> done
> Checking in test.txt;
> /cvs/cvs-test/jhyslop/test_tags/test.txt,v  <--  test.txt
> initial revision: 1.1
> done
> 
> E:\cvs\cvs-test\jhyslop\test_tags>cvs tag rev_1
> T test.txt
> 
> E:\cvs\cvs-test\jhyslop\test_tags>cvs up -r rev_1
> 
> E:\cvs\cvs-test\jhyslop\test_tags>del test.txt
> 
> E:\cvs\cvs-test\jhyslop\test_tags>cvs remove test.txt
> cvs server: use 'cvs commit' to remove this file permanently
> 
> E:\cvs\cvs-test\jhyslop\test_tags>cvs ci -mGawn test.txt
> 
> E:\cvs\cvs-test\jhyslop\test_tags>cvs lo test.txt
> 
> RCS file: /cvs/cvs-test/jhyslop/test_tags/test.txt,v
> Working file: test.txt
> head: 1.1
> branch:
> locks: strict
> access list:
> symbolic names:
> keyword substitution: kv
> total revisions: 1;     selected revisions: 1
> description:
> ----------------------------
> revision 1.1
> date: 2004/11/30 16:17:56;  author: jhyslop;  state: Exp;
> Adding file
> ============================================================================
> =
> 
> E:\cvs\cvs-test\jhyslop\test_tags>
> 
> 
> Note that the log shows the state of 1.1 as Exp, and the tag has
> disappeared. Basically, it looks like a "cvs remove" when there's a sticky
> tag in effect acts the same as a "cvs tag -d [tag]". You get the same
> results even if there's a revision 1.2, i.e.:
> 
> cvs add file
> cvs tag atag file
> [modify file]
> cvs ci file
> cvs up -r atag
> cvs remove -f file
> cvs ci file
> cvs log file (will show 1.1 and 1.2 as state: Exp, no symbolic names).
> 
> This is using CVS 1.11.9 (I know, I know, it's old). I didn't see anything
> in the NEWS file to indicate this problem has been fixed.
> 
> -- 
> Jim Hyslop
> Senior Software Designer
> Leitch Technology International Inc. ( http://www.leitch.com )
> Columnist, C/C++ Users Journal ( http://www.cuj.com/experts )
> 
> 
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/info-cvs
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFBrK9i3x41pRYZE/gRArb1AKCwsNy4em6IOE0qYaaX2A8plNYHnACeMWlX
VxXUGw4PBHC8tcG3ByB9/1M=
=y8iY
-----END PGP SIGNATURE-----