Re: sticky problem: removing -kb option from text file

[David Koski]

On Tue, 18 Jun 2002 18:14:17 -0400 (EDT)
address@hidden (Larry Jones) wrote:

> David Koski writes [using very long lines]:
> > 
> > I have tried:
> > 
> > cvs admin -kkv file.txt
> > cvs update -kkv file.txt
> > 
> > ..without success.
>
> What, exactly, does "without success" mean?  Did you get an error

Seems to be the same as doing nothing at all.  cvs status still showed stick 
option '-kb' as if I had done nothing.

> message, or did it just not do what you expected?  What do:
> 
>       cvs status file.txt
>       cvs log -h file.txt
> 
> show?

With a different file, same problem:

> cvs status test.dat
===================================================================
File: test.dat          Status: Up-to-date
 
   Working revision:    1.1.2.1
   Repository revision: 1.1.2.1 /usr/local/cvs/firedist/Attic/test.dat,v
   Sticky Tag:          SCFD_1_0 (branch: 1.1.2)
   Sticky Date:         (none)
   Sticky Options:      -kb

> cvs admin -kkv test.dat
RCS file: /usr/local/cvs/firedist/Attic/test.dat,v
done
> cvs update -kkv test.dat
U test.dat
> cvs status test.dat
===================================================================
File: test.dat          Status: Up-to-date
 
   Working revision:    1.1.2.1
   Repository revision: 1.1.2.1 /usr/local/cvs/firedist/Attic/test.dat,v
   Sticky Tag:          SCFD_1_0 (branch: 1.1.2)
   Sticky Date:         (none)
   Sticky Options:      -kkv
 
> cvs log test.dat
 
RCS file: /usr/local/cvs/firedist/Attic/test.dat,v
Working file: test.dat
head: 1.1
branch:
locks: strict
access list:
symbolic names:
        SCFD_1_0: 1.1.0.2
keyword substitution: kv
total revisions: 2;     selected revisions: 2
description:
----------------------------
revision 1.1
date: 2002/06/18 22:32:23;  author: dkoski;  state: dead;
branches:  1.1.2;
file test.dat was initially added on branch SCFD_1_0.
----------------------------
revision 1.1.2.1
date: 2002/06/18 22:32:23;  author: dkoski;  state: Exp;  lines: +2066 -0
test of -kb status
=============================================================================
 
> That should have set the default keyword expansion mode on the RCS file
> and the current keyword expansion mode on your working file to the
> default key + value and remove the binary flag.  "Converting" a file
> from binary to text may not do anything sensible -- you may have to
> check in a new version of the file that's a normal text file.

The file is a normal text file.  Only the sticky option is in error.

Regards,
David Koski
address@hidden