info-cvs
[Top][All Lists]
Advanced

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

Re: Permissions on "cvs watch on/off" (Was: Repository know who has che


From: Robert Searle
Subject: Re: Permissions on "cvs watch on/off" (Was: Repository know who has checkouts?)
Date: Fri, 06 Oct 2000 10:12:44 +1200

Thank-you for nailing the reason for putting the cvs edit patches into
the mainstream release of cvs.
I really need to provide sequential editing facilities for
binary/unmergeable files (read locking if you like) and
it is desirable to stay on the main cvs release path (I do not like
maintaining tools at the source patch level thanks, I
am supposed to be working)

With the patches - I get locking like features and can disable the cvs
admin calls, especially the nasty ones like admin -o
Without the patches - I get locking like features (which don't work
properly) and occasional restore from backup nightmares

The only downside to the patches is that cheats can benefit until they
get stomped on for not following the rules

ie. If I lock a file and you don't, I get the check-in, you get the
merge
    If I edit a file and you don't, You get the check-in (if you
override commit -c), I get the merge



reply via email to

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