On Feb 22, 2004, at 5:39 AM, Arvindh Rajesh Tamilmani wrote:
I didn't specify -kb when I added the images.
I suppose that's it.
$ cvs admin -kb # corrects the repository
$ cvs update -A # updates the working copy
should fix the problem.
But I wonder how -kCOPY got into the repository
Done, thanks.
On 22 Feb 2004, at 14:39, Arvindh Rajesh Tamilmani wrote:
I didn't specify -kb when I added the images.
I suppose that's it.
$ cvs admin -kb # corrects the repository
$ cvs update -A # updates the working copy
should fix the problem.
But I wonder how -kCOPY got into the
>I didn't specify -kb when I added the images.
>I suppose that's it.
$ cvs admin -kb # corrects the repository
$ cvs update -A # updates the working copy
should fix the problem.
But I wonder how -kCOPY got into the repository in the
first place. Is CVSROOT/cvswrappers wrong with
som
My fault. I didn't specify -kb when I added the images. I suppose
that's it.
I'll hold off trying to fix it for the moment, in the hope that someone
with more CVS knowledge will beat me to it.
Mike
On 21 Feb 2004, at 23:05, Steve Fink wrote:
.
.
.
P docs/pmc/subs.pod
cvs server: internal
.
.
.
P docs/pmc/subs.pod
cvs server: internal error: unsupported substitution string -kCOPY
U docs/resources/parrot.small.png
U docs/resources/perl-styles.css
cvs server: internal error: unsupported substitution string -kCOPY
U docs/resources/up.gif
.
.
.
Should those perhaps be -kb o
