>Anyway, I haven't discussed these patches with any other CVS developers, so >I don't really know. I also haven't analyzed the code for problems and Noel is >right about the requirement for test cases. I keep thinking about asking for a >consensus, taking a look myself, and trying to coordinate enough with Noel to >make the analysis easier but I haven't found the time. > >That said, my personal feel is that there seems to be enough general interest that >there really doesn't seem any harm in adding most of this functionality as >I understand it. It probably isn't going to happen unless somebody (besides >myself if it is to happen any time soon) decides to clean up the code into a small >number of inteligently grouped patches and adds test cases, however. I haven't >heard any talk among the other developers, in addition to not having brought it up >yet. As with anything open source, I submit no guarantees, but I'll see if I can dig up some time to consolidate the patches. I'm assuming you would rather have one patch (against cvs-1.11) for each new feature set or bug fix than one big patch? I can pretty much say right now, though, that I won't have time to create tests for these, but I would be able to provide specs for such tests. 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. Incorporated, its subsidiaries and affiliates. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
