[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Future CVS Development
From: |
Noel L Yap |
Subject: |
RE: Future CVS Development |
Date: |
Mon, 18 Jun 2001 12:09:58 -0400 |
>> Or how 'bout using the edit and commit patches that more or
>> less give you
>> advisory locks. I'm thinking you may also want to add (if
>> it's possible without
>> breaking something like client/server) a server-side config
>> that would make
>> these flags a default.
>Now there's the rub... it requires patches to get advisory locks. I'm
>talking about baseline CVS, as shipped out-of-the-box. And, the patches
>aren't necessarily kept up-to-date with the latest CVS.
Yes, I would very much love seeing these patches as part of CVS proper. They're
missing test and toc patches (and another volunteer will need to submit these).
Once these are in, the patches'll have a bigger chance of being included.
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.
- Future CVS Development, Kostur, Andre, 2001/06/18
- Re: Future CVS Development, Noel L Yap, 2001/06/18
- RE: Future CVS Development, Kostur, Andre, 2001/06/18
- RE: Future CVS Development,
Noel L Yap <=
- RE: Future CVS Development, Kostur, Andre, 2001/06/18
- RE: Future CVS Development, Kostur, Andre, 2001/06/19
- Re: Future CVS Development, Alexander Kamilewicz, 2001/06/20