Re: reserved lock and other patches

[Noel L Yap]

OK, the strategy I've picked is to submit three separate patches:
1. "multiple_edits" which will allow multiple edits per user per file.
2. "reservations" which will allow users to have "reserved" locks on files.
3. "multiple_edits+reservations" which will have both of the above (minus merge
conflicts, of course).

If anyone has a better suggestion, I'd like to hear it.

Thanks,
Noel




address@hidden on 2001.03.06 18:55:36

To:   address@hidden
cc:   (bcc: Noel L Yap)
Subject:  reserved lock and other patches




I'm finally spending some time cleaning up my patches available on
sourceforge.com under project RCVS.  I have a RFC about organising some of the
bigger enhancements.  I see the following as the two biggest enhancements:
1. Users are allowed to edit files multiple times.  The edit information is
composed of username, client hostname, and working directory to achieve this.
2. Users are allowed to have reserved edits.  To the user, this is in the form
of the added options "cvs edit -c", "cvs edit -f", and "cvs ci -c".

My question is this:  "cvs ci -c" will check for a valid edit.  The term "valid
edit" will change upon using the "multiple edits" patch.  Does anyone have any
suggestions on how to organise the branching/patches in this scenario?

Thanks,
Noel



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.


_______________________________________________
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.