bug-cvs
[Top][All Lists]
Advanced

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

Re: advisory locks patch


From: Derek Robert Price
Subject: Re: advisory locks patch
Date: Mon, 04 Oct 2004 21:44:54 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Derek Robert Price wrote:

> >I am curious if it would be possible to have a commitinfo trigger catch
> >the condition of a user 'forgetting' to use 'cvs commit -c' and enforce
> >it as an administrator policy for one or more modules of a repository,
> >or even for particular file types. That is, would a 'cvs -n editors'
> >command provide enough information to know that the 'cvs edit -c' was
> >in force by some other user?
>
> A format string that passed the -c option into commitinfo if present


I reread this with less on my mind and noticed that this should be
possible to do by having commitinfo call `cvs editors' and grep the
name now that commit uses promotable locks.

I suppose it might be easier for CVS, so a boolean flag passed to
commitinfo that means "this user has a valid edit on this file" might
be still useful.

Cheers,

Derek
- --
                *8^)

Email: address@hidden

Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBYfyWLD1OTBfyMaQRAvIKAKDnT0/07yfXeHU7CA5iSHwBeAd+4QCfeIpP
QVG9lvj+hgklaKu/3JHrm54=
=Gz6M
-----END PGP SIGNATURE-----





reply via email to

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