Re: Réf. : Re: cvs editors bug? renegade cvs or 1.11?

[Noel L Yap]

This is both the curse and the blessings of open source development.  On one
hand, you are able to fix problems on your own.  On the other hand, you many
need to maintain those fixes.

I can't completely blame the CVS maintainers for not using my patches.
According to the HACKING file, I'm supposed to submit patches to the regression
tests as well.  I haven't had time to do this (nor does it look like I'll have
any time in the near future).

Anyway, I think Derek Price will know more about the status of these patches in
the standard CVS release.

Noel


thank you for your help!
 Who better than you could have answered to my metaphisical interrogations ;)
It's very disapointing to learn that known and fixed bugs are not retrofit to
the main cvs branch :)
How can I explain this to the (numerous) cvs users here?
...
well I guess my best guess is to do as you say o:)
but I have very little time to devote to this kind of home made soups.
the only solution I see to keep the burden of versions upgrading to the minimum
is to stick to std sources
do you think your changes are to be included in the next main cvs release?
if not this is rellay a shame :(
btw I have home made patches for the inetd line length pbm and I have to merge
them back eah time a new CVS is out
why don't they react to requests?

thx

     Oliv







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.