From: Daniel J S. <dan...@ie...> - 2004-06-02 20:10:57
|
Hans-Bernhard Broeker wrote: >>Anyway, simple bug fixes usually can be handled by "patch" with >>realignment, but something like ANSIfying the code would certainly cause >>problems for a large percentage of the patches in SourceForge. >> >> > >Most of them will require tweaking anyway. The only real question is how >much of it. > > > >>This would be nice. I'd opt for clearing the patch page over the course >>of a couple months. Then ANSIfy and restructer code. >> >> > >While clearing the known bugs is a viable goal, I don't see that for the >patches tracker. Some of those will simply not be integrated, or are too >far out of date to be applied cleanly. The patches tracker is as much a >service to enterprising users as to us --- it's a means of collecting >unofficial changes that won't go in the mainline source code, as much as >one of collecting bugfixes that will have to be. > What I mean by clearing is to weed out those that, as you mention, will never get implemented because they are so out of date or are now irrelevant. Discuss those that might be integrated, if yes then give the owner a chance to update the patch and hold cvs stable for a few days. (Not everyone trying to update patches at once would be good too.) Dan -- Dan Sebald email: daniel DOT sebald AT ieee DOT org URL: http://acer-access DOT com/~dsebald AT acer-access DOT com/ |