info-cvs
[Top][All Lists]
Advanced

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

Re: Dis-allow Commit check for $id$


From: Mark D. Baushke
Subject: Re: Dis-allow Commit check for $id$
Date: Wed, 02 Aug 2006 11:43:49 -0700

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matthew Rich <address@hidden> writes:

> If the file was added with out the -ko switch
> being set, it still requires the $Id$ be present
> on commit.

That will be entirely up to how you are using your
CVSROOT/commitinfo trigger your administrator has
specified. It is not a part of the default cvs
installation.

> 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.

Okay. So, fix the scripts run by commitinfo to be
more reasonable.

> 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.

Beat on your administrator to properly handle binary files.
CVS has no problems by default.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (FreeBSD)

iD8DBQFE0PJlCg7APGsDnFERAq7QAKCdOdVMqzLW2cMRbFcOUN2EUe1mEwCgxTD7
7A2oRexrKpqNIbgN7qF0mqw=
=45tf
-----END PGP SIGNATURE-----




reply via email to

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