Re: commitinfo and file locking

[Noel L Yap]

Locks are in place before commitinfo is started.

Noel


|--------+----------------------->
|        |                       |
|        |          address@hidden|
|        |          et           |
|        |                       |
|        |          07/16/01     |
|        |          05:03 PM     |
|        |                       |
|--------+----------------------->
  >----------------------------------------------------------------------------|
  |                                                                            |
  |       To:     address@hidden                                             |
  |       cc:     (bcc: Noel L Yap)                                            |
  |       Subject:     commitinfo and file locking                             |
  >----------------------------------------------------------------------------|






Just a quick functionality question...

Files within the repository must obviously be locked during the
actual commit, but is this lock already in place during the
commitinfo phase of things?

(The point here is that I would like a script in commitinfo to copy
the old version of the ,v file elsewhere before the commit is
applied, but I don't want to have more than one client be able to
get through the commitinfo stage before hitting another user's lock,
meaning that my copied file is inconsistent. Yes, I really do need
to do this on the server side rather than doing a later cvs diff
on the client side.)

--
       ~ g r @ eclipsed.net

_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs




This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.