Noel L Yap wrote:
> 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?
Yeah, that's what I meant. A patch per feature set is much easier to deal with.
As for bug fixes, if it fixes a bug that you introduced with a feature add, they
should be grouped. If it is an unrelated bug fix, keep it separate.
> 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.
As I said, it is unlikely that I will find time soon to do the test cases my self,
either, but the likelihood of a patch getting into the main distribution seems to
be a function of developer time & expertise, the need for the feature/bug fix, and
the patch's usability, size, and readability, among other things. In other words,
an organized submission with test cases would help more, but an organized
submission should move things along anyhow. Even if the changes weren't
incorporated immediately, it would make it easier for some other developer who
wanted a particular feature to add the test cases just for the appropriate patch
and resubmit it, for example.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
Smash forehead on keyboard to continue.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
