> - If you are duplicating existing functionality in some way to make things > "better", then people will not feel comfortable replacing some stuff that's > already there and thought to be working (more or less). You need to create > your patch file in such a fashion that it can be switched on or off to use > the "existing" code, and not yours. Again, people may be more willing to > accept your patch. In other words, don't patch smsc_at.c; create a new file > (smsc_at2.c or something similar) that can be used instead, and create a new > smsc definition for the configuration file so that people can experiment > more readily.
I agree with Nick here. We have to keep current "working" operatibility and "add" features. This does not mean that if the new feature has been proven to be "better" the old one would be skipped. The list had lost some words about that already. smsc_at3.c would be suggestable. Stipe [EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG M�nsterstr. 248 40470 D�sseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are
