From: Doug Evans <dje@google.com>
To: gdb-patches@sourceware.org
Subject: [RFC] Change coding style rule: 80 column "hard limit" for ChangeLogs
Date: Fri, 03 Jan 2014 22:50:00 -0000 [thread overview]
Message-ID: <yjt261q0r886.fsf@ruffy.mtv.corp.google.com> (raw)
We have so many style rules, IWBN to simplify things where possible.
Does anyone know the origin of the 74 column "hard" limit for ChangeLogs?
I propose we change that to 80 to match the rule for code:
one column limit for everything.
I'm referring to the "hard" limit here. Apparently there's a 70-character
soft limit for code:
https://sourceware.org/gdb/wiki/JoelsCodingStyleCheatSheet#Maximum_line_length
next reply other threads:[~2014-01-03 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 22:50 Doug Evans [this message]
2014-01-04 7:22 ` Eli Zaretskii
2014-01-05 4:00 ` Joel Brobecker
2014-01-06 17:56 ` Doug Evans
2014-01-08 11:45 ` Joel Brobecker
2014-01-08 20:21 ` Doug Evans
2014-01-08 21:42 ` Sergio Durigan Junior
2014-01-09 2:34 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yjt261q0r886.fsf@ruffy.mtv.corp.google.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).