[Top][All Lists]

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

Re: Lock a tree read-only for historical purposes

From: Mark D. Baushke
Subject: Re: Lock a tree read-only for historical purposes
Date: Sat, 23 Oct 2004 00:40:15 -0700

Hash: SHA1

Vicki Brown <address@hidden> writes:

> Is there any way with CVS to lock a tree so that
> no additional changes can be checked in for
> files on that tree?

Yes. There are multiple ways to accomplish this.

1) You can use the commitinfo script to do this.
You may wish to look at the contrb/
script for this purpose:

2) Another way to do it would be to change the
directory ownership, group and world permissions
so that you do not allow read-write to anyone.

Before you do it, you would point your
CVSROOT/config at a LockDir that allows writes.
This will let folks checkout the sources without
any modifications at all being allowed.

3) Burn the repository to a read-only media and
have folks checkout the trees via read-only NFS
or some other mounting method of your choice using
the 'cvs -R' option.

> Specifically, lets say I have a tree of files
> for an "old" project. The project is closed. If
> anyone plans to revive something from that
> project they should make a copy into a new tree
> and start from there. But I don't just want to
> clear out the old tree. I'd like to preserve the
> history but do so in a read-only state. I want
> to set this part of my tree in amber.
> Can I do that?


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


reply via email to

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