Hi all,
I've checked the list archives and the CVS manual for a solution to this
problem, and I haven't discovered a solution, so hopefully someone has
seen this problem before.
Here's my command history, with typos removed and commentary added
(using C++ style comments :-).
80 14:11 mkdir testcode // make a new project directory
somewhere
81 14:12 cat > testcode/junk.c // create a new file in the
project
83 14:13 cd testcode
85 14:13 cvs import testcode kivera initial // import the new
project
87 14:14 cd ..
88 14:14 cvs co testcode
90 14:14 cat >> testcode/junk.c
91 14:15 cvs diff testcode/
92 14:15 cvs commit -m "Yada" testcode/junk.c
93 14:15 cvs log testcode/junk.c
95 14:16 cvs tag -b firstbranch testcode // tag the branch
96 14:16 cvs update -r firstbranch testcode/ // get a working
copy of the branch
97 14:16 cvs status testcode
The output of the status command is what I expected to see:
cvs status: Examining testcode
===================================================================
File: junk.c Status: Up-to-date
Working revision: 1.2 Tue May 9 21:14:52 2000
Repository revision: 1.2
/net/home/export/home/mhartfie/testjunk/testcode/junk.c,v
Sticky Tag: firstbranch (branch: 1.2.2)
Sticky Date: (none)
Sticky Options: (none)
98 14:16 cat >> testcode/junk.c // commit some changes and
tag a release (not a branch)
99 14:17 cvs commit -m third testcode
100 14:17 cvs tag firstrelease testcode
101 14:18 cvs update -r firstrelease testcode // get a working
copy of the release
102 14:18 cvs status testcode
The output of the status command is again what I expected to see:
cvs status: Examining testcode
===================================================================
File: junk.c Status: Up-to-date
Working revision: 1.2.2.1 Tue May 9 21:16:53 2000
Repository revision: 1.2.2.1
/net/home/export/home/mhartfie/testjunk/testcode/junk.c,v
Sticky Tag: firstrelease (revision: 1.2.2.1)
Sticky Date: (none)
Sticky Options: (none)
103 14:18 cat >> testcode/junk.c
104 14:18 cvs commit -m fourth testcode
The commit fails with the following error:
cvs commit: Examining testcode
cvs commit: sticky tag `firstrelease' for file `testcode/junk.c' is not
a branch
cvs [commit aborted]: correct above errors first!
What's the deal? Is it not kosher to add a symbolic tag to a branch?
If not, that would be a serious limitation. We have new development
occuring on the branch, which we want to tag each milestone. We
concurrently have bug fixes occurring on the main trunk to our released
product, and we need to tag those to mark our incremental releases.
Any ideas?
Thanks,
Matt Hartfield
--
Matt Hartfield
Kivera, Inc.
[EMAIL PROTECTED]
