[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dis-allow Commit check for $id$

From: Matthew Rich
Subject: Re: Dis-allow Commit check for $id$
Date: Wed, 2 Aug 2006 11:25:13 -0700 (PDT)

If the file was added with out the -ko switch being set, it still requires the  
$Id$ be present on commit.  if  I try cvs admin -ko filename and then I commit 
it still requires that the key word be present.  If i do a cvs status it shows 
the sticky flag ko.
   Do I need to remove the file and add it again?  it there any way around this 
key work issue? Or am I  stuck with having to edit the file after it is checked 
out to remove the key word. 

----- Original Message ----
From: Mark D. Baushke <address@hidden>
To: Matthew Rich <address@hidden>
Cc: address@hidden
Sent: Tuesday, July 18, 2006 7:42:57 PM
Subject: Re: Dis-allow Commit check for $id$ 

Hash: SHA1

Matthew Rich <address@hidden> writes:

> I have a set of sources to check into a new repository that I don't
> want key work expansion to function. This source tree is a mix of
> sources and binaries. We may need to make some changes to the sources
> but we do not want to have to add the key work $Id$ to each file. Will
> importing using the -kb switch for all the files accomplish this?

The -kb switch is primarily intended for binaries. If you use it for all
files, then the line endings will not be converted for you.

If you can import the source separately from the binary, you may wish to
use -ko for the source files.

    -- Mark
Version: GnuPG v1.4.4 (FreeBSD)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]