info-cvs
[Top][All Lists]
Advanced

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

Re: cvs editors bug? renegade cvs or 1.11?


From: Noel L Yap
Subject: Re: cvs editors bug? renegade cvs or 1.11?
Date: Mon, 15 Jan 2001 18:34:38 -0500

The edit patches I submitted were to address deficiencies in cvs-1.10.8.  AFAIK,
none of these patches have made their way into cvs-1.11.  If you want to use
cvs-1.11 with the patches, I think the easiest way would be to import
cvs-1.10.8, install the patches, import cvs-1.11, then merge.

Noel




address@hidden on 2001.01.15 02:45:55

To:   address@hidden
cc:   (bcc: Noel L Yap)
Subject:  cvs editors bug? renegade cvs or 1.11?







I'm in charge of (some sort of) CVS support for a team of coders.
They report some strange behaviors regarding cvs edit/unedit.
(the list of editors is not in sync with reality)
I'm watching this ML for some times and never noticed anything on this topic
(edit bug)
I assumed that the problem was not due to cvs but to ... errr... users ;)
But today I checked for the renegade CVS on source forge and found a lot of
patches like:
- cvs edit fixed to save correct working directory
- "cvs edit" fixed so wd are purely absolute
- various "cvs edit" & "cvs unedit" bugs fixed
- ...
I'm running the 1.11 server (the problems were also reported for 1.10.8)
What must I conclude?
The rcvs bug fixes are related to code specific to rcvs branch?
Or do they also apply to pure cvs ? And is the 1.11 already patched?

Thanx for any hint on this topic

     Olivier





_______________________________________________
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. Incorporated, its
subsidiaries and affiliates.




reply via email to

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