Re: [PATCH] Add line-wrapping guidelines to the coding style documentation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Wincent Colaiuta <win@xxxxxxxxxxx> writes:

> A statistician could probably make some interesting comments about the  
> results, but the basic trend is that, while there are plenty of  
> examples of isolated long lines in the source tree (the longest is a  
> 287-character line in one of the perl scripts), the frequency starts  
> to drop off pretty rapidly once you pass 70 columns and start climbing  
> towards 80.

Gaah.  287???

> + - In the case of documentation, mixing excessively long and short
> +   lines may make the AsciiDoc source harder to read, so try to
> +   keep line lengths consistent.
> +
> + - When submitting patches use common sense to decide whether to
> +   rewrap, avoiding gratuitous changes.

Hmph.  The last item applies only to the documentation because
it uses the word "rewrap", but otherwise applies equally well to
the sources (re-indenting).  So probably "whether to rewrap or
reindent" would be a good change there.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux