On Tue, May 09, 2000 at 02:35:35PM -0700, Matt Hartfield wrote:
> 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?
Sure it is.
The sticky tag simply points to a particular revision of a file and not
to a branch, so if you commit your change with giving information about
the branch where to put it, it will work. Try
cvs ci -m "fourth" -r firstbranch testcode/junk.c
and you should get something like
cvs commit: Examining testcode/
Checking in junk.c;
/usr/local/test_repository/testcode/junk.c,v <-- junk.c
new revision: 1.2.2.2; previous revision: 1.2.2.1
done
A 'cvs status' produces then
cvs status: Examining .
===================================================================
File: junk.c Status: Up-to-date
Working revision: 1.2.2.2 Wed May 10 07:02:37 2000
Repository revision: 1.2.2.2
/usr/local/test_repository/testcode/junk.c,v
Sticky Tag: firstbranch (branch: 1.2.2)
Sticky Date: (none)
Sticky Options: (none)
Have fun,
Matthias
--
Matthias Kranz [EMAIL PROTECTED]
http://www.belug.org/~kranz
"Ever tried. Ever failed. No matter. Try again.
Fail again. Fail better." (Samuel Beckett)
