[cvsnt] PreservePermissions=yes/no vs cvs edit / files not read-only

Thierry Moreau Thierry.Moreau at Connotech.com
Sat Jan 11 21:22:22 GMT 2003

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


A recurring issue in this newsgroup appears about PreservePermissions
and cvs edit followed by cvs commit not leaving files in read-only mode.

I tried to set up PreservePermissions=no, then PreservePermissions=yes
in the administrative file CVSROOT/config (with a cvs commit which
reported "cvs commit: Rebuilding administrative file database"). I
looked at the file CVSROOT/.#config which seems to ignore or reverse the
setting (!).

In either case, the "permissions 666;" gets in the repository whenever a
commit is done.

Now my cvs repository has some files with permissions 666; and others
not (from older RCS data files).

Is there any chance that this issue can be clarified?

(A) Clarifications about PreservePermissions and how to set it.

(B) Support status of cvs watch on/off and cvs edit/unedit in cvsnt
(this is the main issue, a well documented feature of CVS for which many
cvsnt users experience problems)

(C) Mechanisms to manipulate and/or purge the "permissions 666;" in the

I quote Open Source Development With CVS:

PreservePermissions governs whether to preserve file permissions and
similar metadata in the revision history. This is a somewhat obscure
feature that probably isn't worth describing in detail.



- Thierry Moreau

CONNOTECH Experts-conseils inc.
9130 Place de Montgolfier
Montreal, Qc
H2M 2A1

Tel.: (514)385-5691
Fax:  (514)385-5900

e-mail: thierry.moreau at connotech.com

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook