RE: bug in com_lglx5450.py
"Simon C" <[email protected]>
| Newsgroups | gmane.comp.mobile.bitpim.devel |
|---|---|
| Message-ID | <000901c5fb43$0db95ec0$6400a8c0@HOME> |
> > What is considered proper etiquette when finding a bug in someone else's > code in BitPim? > > Everyone is egoless :-) The only criteria you should use is whether code > you are > suggesting/adding improves BitPim. If it does then everyone will be happy > for it. > (Bug fixes easily fit that criteria). Yup we don't have egos, only EGOs. :) > > I am using Tortoise CVS > > The CVS eol rules on Windows are simple. Either use entirely native > Windows CVS > (Tortoise counts), Windows editor etc or use entirely UNIXy (cygwin & > family) > versions of cvs and editors. If you mix and match then a line ending > nightmare > happens in the repository and to all other people who check the code out. > > Subversion fixes all these silly issues and SourceForge keep promising it > real > soon now. I had the same problem e-mail source. I use dos2unix (get cygwin, mingw or similar) to convert source files before e-mailing. Simon ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click