[Xen-changelog] [xen staging] libxl: CODING_STYLE: Clarify line length limit to 75

[patchbot@xxxxxxx]

commit a23744e9ee82938f22c9f8303d1b3a1c033f3b32
Author:     Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
AuthorDate: Mon Oct 15 14:51:01 2018 +0100
Commit:     Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
CommitDate: Tue Oct 30 17:03:23 2018 +0000

    libxl: CODING_STYLE: Clarify line length limit to 75
    
    And give a reason.
    
    The previous `limit' of 75-80 was ambiguous.
    
    Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    CC: Anthony PERARD <anthony.perard@xxxxxxxxxx>
---
 tools/libxl/CODING_STYLE | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/tools/libxl/CODING_STYLE b/tools/libxl/CODING_STYLE
index 32170efb9e..3d572f6925 100644
--- a/tools/libxl/CODING_STYLE
+++ b/tools/libxl/CODING_STYLE
@@ -220,12 +220,14 @@ Do not leave whitespace dangling off the ends of lines.
 
 2. Line width
 
-Lines are limited to 75-80 characters.
+Lines are limited to 75 characters.
 
 Rationale:
  - Some people like to tile their 24" screens with a 6x4 matrix of 80x24
    xterms and use vi in all of them.  The best way to punish them is to
    let them keep doing it.
+ - In an 80 column terminal, some room needs to be left for > quoting
+   characters, +/- diff characters, and so on, in emails.
  - Code and especially patches is much more readable if limited to a sane
    line length.  Eighty is traditional.
  - It is the libxenlight coding style.
--
generated by git-patchbot for /home/xen/git/xen.git#staging

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/xen-changelog