RE: [RFC] CVS rules for STATUS
"Oded Arbel" <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi. If people agree, I'd like to at least note the SIM buffering patch I submitted to the list in STATUS (msgid : [email protected]) BTW - I was wondering - how many people (count, not interested in names :-) have CVS write access ? TIA Oded Arbel m-Wise Inc. [email protected] -- Ninety eight percent of the adults in this country are decent, hardworking, honest Americans. It's the other lousy two percent that get all the publicity. But then, we elected them. -- Lily Tomlin > -----Original Message----- > From: Stipe Tolj [mailto:[email protected]] > Sent: Wednesday, February 20, 2002 1:25 AM > To: [email protected] > Subject: [RFC] CVS rules for STATUS > > > I would like to advice that changes to the STATUS file in the gateway > CVS module should *not* be logged to ChangeLog, two main reasons: > > 1) STATUS is not considered to be module specific code and hence > ChangeLog messages about this file would fuzzy up the meaning of > ChangeLog, IMO. > > 2) Acceptance for CVS contributors to keep STATUS up to date (which is > the main intension) is raised, because double editing (STATUS and > ChangeLog) is not required. > > So, heads up if there are complains about this rule. > > BTW, I haven't seen anyone from the CVS write permission users to > update STATUS?! > Please keep it up to date, it is ment to be a postulation file of the > current issues that are discussed and tracked at the developers list. > Especialy the "Status:" fields should be edited by the corresponding > responsible parties of the single modules. > > 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 > >