lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetic <otis_gospodne...@yahoo.com>
Subject Re: Code Format for Contribution
Date Mon, 21 Jun 2004 16:14:13 GMT
Rasik,

No tabs, no ^Ms, 2 spaces for indentation, { on the same (not new)
line, and that's about it.  When submitting a diff, it's good to limit
the changes to functionality only, and minimize irrelevant code changes
(e.g. style, spaces, etc.).  That's about it.

Otis

--- Rasik Pandey <rasik.pandey@ajlsm.com> wrote:
> Hello,
> 
> I have spent some time refactoring code in the
> org.apache.lucene.analysis package from both the lucene core and
> sandbox. I was wondering if a document exists detailing the code
> format for Lucene, so that my patch diffs as well as new files will
> be easier to read.
> 
> Regards,
> RBP 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org


Mime
View raw message