This statement seems uncogent.
Users sending patches to a list, should they emerge, should be sending diffs against the published CVS source, not diffs against unofficially patched code. In a context like the Linux kernel, where there is a lot of development going on in multiple tracks, you can see clearly that users submit diffs against a specific tree--Linux, Alan, other whatever. If a maintainer gets a patch that doesn't apply cleanly to his tree, its his choice whether to work out why it doesn't apply, ask for a clean patch, or throw it away. Maintainers aren't going to rely on developers who send bad patches, as a rule. If a situation evolved where SAPDB was being developed on track(s) outside of SAP, people submitting a patch on that sort of code should send it to the maintainer(s) of the side branch, not SAP. Matt On Wed, 24 Oct 2001, Schaefer, Peter wrote: > Hello! > > > And i would go one step further -> don't install a public CVS server > before you don't have a good way to catch regressions (at least a simple > SQL scripts based one - like the regression tests of PostgreSQL). > > Otherwise you'll have to ask "Which patches have you made ?" if one > poster comes up with an bug report :). > > Peter Sch�fer > EADS Radio Communication Systems GmbH & Co. KG > > *NOT SPEAKING FOR MY EMPLOYER* > Matt Benjamin The Linux Box 206 South Fifth Ave. Suite 150 Ann Arbor, MI 48104 tel. 734-761-4689 fax. 734-769-8938 pgr. 734-431-0118
