From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Eli Zaretskii <eliz@gnu.org>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFC] Change coding style rule: 80 column "hard limit" for ChangeLogs
Date: Wed, 08 Jan 2014 21:42:00 -0000 [thread overview]
Message-ID: <m3ob3mrw04.fsf@redhat.com> (raw)
In-Reply-To: <CADPb22R2ES=5S6sqUwfaRHcmCJCa5ssLWqgV3ZBaf1yUkJtA0g@mail.gmail.com> (Doug Evans's message of "Wed, 8 Jan 2014 12:21:26 -0800")
On Wednesday, January 08 2014, Doug Evans wrote:
> So how about a 74 soft limit and 80 hard limit for everything (modulo
> things like .exp files where we try to keep things under 80 but some
> lines are just long and best left as is).
I'm following the discussion, and I'm happier with this rule.
FWIW, I try to keep things under 76 chars, but that's only my personal
rule :-).
--
Sergio
next prev parent reply other threads:[~2014-01-08 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 22:50 Doug Evans
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 [this message]
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=m3ob3mrw04.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--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).