Hi Derek, > From: Derek Price > > >2. If no one steps forward to assist with building should > >we attempt a fix that can't be tested nevertheless? > > The policy, as I thought was documented in HACKING or somesuch, is that > we do not bother. I can't find the original text in a quick scan, however. > > In general, if there is no way to tell if it works, what is the point? > In reality, I ocassionally cut and paste a new function or API change > when I change it elsewhere, but more often lately, I don't bother. If > someone decides to fix the platform up, it should be easy enough to > trace the missing functions to their counter-parts in src, lib. or wherever.
I agree on both points which is part of my motivation to raise the issue. As I see it we have three choices: 1. Do nothing more to "os2/run.c". 2. Add "FIXME: ..." to "os2/run.c". 3. Cut and paste new functions into "os2/run.c" Option 1 penalizes innocent OS/2 newbies by wasting their time when I feel we should reward newbies by easing their entry when economical to do so. I'll implement at least Option 2 by Wednesday. Do you have any preferred language or points you'd want covered in the "FIXME" note? > Cheers, Ditto, > Derek _______________________________________________ Bug-cvs mailing list Bug-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/bug-cvs
