A reminder:
The OpenLDAP source code uses tab-width 4 and generally lines < 80
chars. Please commit code written the same way, except in files
that are already written with tab-width 8.
Some people have been committing with tab-width 8, so the code now
contains a mixture of tab-width 4 an
Please use tab-width 4 like most of the rest of the code. Unless you
are in a tab-width 8 file, anyway. This mixture of tab-width 4 and 8
keeps misaligning more and more of the code, one line here and one there
over the years. In this case the 'struct ldif_tool' contents, which w
Hallvard B Furuseth wrote:
Pierangelo Masarati writes:
Just noticed your indentation... Note that OpenLDAP code looks
best when edited and displayed with tab-width 4, not 8.
I've used a width of 8 since 1999, and it looked just fine since then :)
Including lines - i.e. declarations
Pierangelo Masarati writes:
>> Just noticed your indentation... Note that OpenLDAP code looks
>> best when edited and displayed with tab-width 4, not 8.
>
> I've used a width of 8 since 1999, and it looked just fine since then :)
Including lines - i.e. declarations,
> [EMAIL PROTECTED] writes:
>> Modified Files:
>> backend.c 1.384 -> 1.385
>
> Just noticed your indentation... Note that OpenLDAP code looks
> best when edited and displayed with tab-width 4, not 8.
I've used a width of 8 since 1999, and it looked ju
[EMAIL PROTECTED] writes:
> Modified Files:
> backend.c 1.384 -> 1.385
Just noticed your indentation... Note that OpenLDAP code looks
best when edited and displayed with tab-width 4, not 8.
--
Hallvard
