[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: problem with binary attribute -kb
From: |
Eric Siegerman |
Subject: |
Re: problem with binary attribute -kb |
Date: |
Fri, 19 Oct 2001 13:39:36 -0400 |
User-agent: |
Mutt/1.2.5i |
On Fri, Oct 19, 2001 at 10:44:22AM -0400, Stanton, Curt (NCI/IMS) wrote:
> I have recently switched from RCS to CVS and now a few of my java files have
> the -kb option set. They are java files, so they are text not binary. Is
> there a way that I can issue a command through the client to get rid of any
> -k options?
Well, you can't get rid of it, but you can set it to a more
appropriate value. Use:
cvs admin -k<whatever> file...
> If not would setting the -ko option make the file work the same
> as no -k option?
As I said, I don't think there's such a thing as "no -k option".
Choose -kkv or -ko, depending on whether you want $Id$ and
friends to work "normally" or to be ignored (aka not f**ed with).
There's no Right Answer to that; it depends on your
circumstances. (There are other choices too, but those are
rarely used, in my experience.)
> Another question, one of my files that was set with the
> -kb has in the Repo ,v file a line 'locks; strict;' , while in other files
> it is just 'locks;' What does this mean?
See the rcs(1) man page: -L and -U options. It looks as though
CVS likes to have strict locking turned *on* -- at least, that's
how many of my CVS-created ,v files are set.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. address@hidden
| | /
The world has been attacked. The world must respond ... [but] we must
be guided by a commitment to do what works in the long run, not by what
makes us feel better in the short run.
- Jean Chrétien, Prime Minister of Canada