[Top][All Lists]

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

Re: can particular cvs project files be locked/ignored

From: Pierre Asselin
Subject: Re: can particular cvs project files be locked/ignored
Date: Thu, 21 Sep 2006 00:18:41 +0000 (UTC)
User-agent: tin/1.6.2-20030910 ("Pabbay") (UNIX) (NetBSD/3.0 (i386))

Mark <address@hidden> wrote:

> There are a few files in our project under cvs control
> that are going to be in a frozen state from now on and
> that we don't want to cvs remove and then attic (at least
> not right now)
> By frozen, I mean that if external files of the
> same names are copied on top of them in someone's sandbox,
> I don't want cvs update to try to merge them but rather
> I'd want a cvs update in the directory to either ignore
> the files or just say "file X is locked" or something
> similar.

You can do it sanbox by sandbox, by planting a sticky
tag to the frozen revision.  Normally that should be

    cvs update -r1 file1 file2 ...

(assuming you want to freeze at the tip of the trunk,
and that your trunk revisions are of the form 1.nnn).
To unfreeze a sandbox, remove the sticky tags
    cvs update -A file1 file2 ...

Another way would be to install a commitinfo script that prevent
commits from any sandbox where one of those files has been modified.

pa at panix dot com

reply via email to

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