Re: [Fresco-devel] Coding guidelines again
Tobias Hunger <[email protected]>
| Newsgroups | gmane.comp.video.fresco.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 13 June 2002 11:48, Nathaniel Smith wrote: > > - If a fresh CVS checkout can't be build with [[[COMPILER]]] > > [[VERSION]] or does not run the all demos build as part of > > Clients-C++, immediently supply a minimalistic patch/commit that > > addresses the problem breaking the build/demos and *nothing* else. <snip> > > - Do not commit changes to other people's code without consulting them > > first. Mail your patches to the copyright holder(s) given in the > > file you patched and if those do not react to [email protected]. <snip> > Overall, my ideal choice would be to just ignore these sorts of > questions until we actually encounter problems. > My second choice would be to define the working rule as "If you have > commit privileges, and know what you're doing, commit it. If you > don't have commit privileges, or aren't sure whether you know what > you're doing, send it to the list". Oh, we did allready encounter problems with this. I broke some of stefan's code because I was overenthusiastic with fixing soemthing... But you got a very good point wrt. developer resources. How about this: * Commit/send in patches only addressing one issue at a time.. Justification: It's easier to track issues this way, backout faulty patches, etc. - -- Gruss, Tobias - ------------------------------------------------------------ Tobias Hunger The box said: 'Windows 95 or better' [email protected] So I installed Linux. - ------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9CHFRv0FZW3NyoqURAj2SAJ4qWksUf+HOo5s+v8QRxzJTOMQjiACgt5uj ek+c4KK6RJumu3OecaQ/JB8= =A0qa -----END PGP SIGNATURE-----