[Larry Jones]
> The PreservePermissions code is notoriously buggy and should not be
> used. Recent versions of CVS omit it by default and the manual no
> longer mentions it at all.
Particularly hardlinks must be a quite difficult thing to deal with, but
saving, and later restoring simple file permissions and ownership really
shouldn't be that hard, and I'd daresay it can be a nice feature,
particularly when storing configuration files in cvs.
As a matter of fact, I have absolutely nothing else to do this week, so I
might eventually take a look into the sources and see if I can do anything.
Will patches eventually be accepted?
Another issue about file permissions ... I'd like to keep most of /etc in
cvs. Unfortunately, this includes some few secret files. Checking them in
leaves the ,v-files world-readable. I think it could be wise to let cvs
check for restricted readability of files, and store the ,v-files with the
same permission and ownership as the original files. Well. I guess I could
solve the problem by just leaving the CVSROOT unreadable for anyone else
than the system administrator. Comments?
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
