[previous copy had wrong addressee list, sorry] On Thursday 09 July 2009, Zach Welch wrote: > > > But for the record ... standard process for bug reporters > > in Linux most typically involves getting the submitter to > > build *current* stuff to verify the bug still exists. If > > the kernel isn't current, it's very likely that at least > > some of the symptoms changed; maybe the bug is fully fixed! > > The contributor of a patch is acting as a developer, so they should be > able to build it.
I wasn't talking about someone submitting a patch. That was *specifically* about bug reports. A very common response to a bug report is to first verify that the *current* source still exhibits the problem. If it does, then it's time to develop new patches. And ... surprise, testing those requires testers (who are the folk who submit probem reports!) to be able to apply them and build the result. - Dave > I agree completely that developers should be testing > and submitting patches against the trunk HEAD. _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
