From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>
Cc: 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: Thu, 09 Jan 2014 02:34:00 -0000 [thread overview]
Message-ID: <20140109023417.GP3802@adacore.com> (raw)
In-Reply-To: <CADPb22R2ES=5S6sqUwfaRHcmCJCa5ssLWqgV3ZBaf1yUkJtA0g@mail.gmail.com>
> 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).
>
> soft = "stay within the limit unless you have a reasonable reason to
> exceed, and we're not nitpicky on what reasonable is"
>
> hard = "do not exceed unless you just cannot do otherwise, and while
> there are exceptions, we are quite nitpicky on this one"
>
> Even that wording doesn't preclude different interpretations. I'm
> happy to tweak it. The high order bits for me are the same numbers
> for everything, and not being nitpicky on adherence to the soft limit.
I all works for me.
> If there are no objections, I will tweak your coding style cheat sheet
> wiki (just trying to save you the trouble, it's your page, feel free
> to edit as desired), and update other docs (the CodingStandards wiki
> doesn't exist, I'll create it and add something to get it going).
I don't consider it my property so feel free to edit and improve as
you see fit. The purpose is to have something as useful as possible
to others, and also as a way to keep track of past discussions that
lead to the various rules (hence HTML instead of texi). I initially
created it and put my name next to it to make it extra clear that
it's unofficial and WIP.
Now that gdbint has been moved to the wiki, I should probably think
of merging this with the rest of gdbinit at some point.
Thanks!
--
Joel
prev parent reply other threads:[~2014-01-09 2:34 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
2014-01-09 2:34 ` Joel Brobecker [this message]
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=20140109023417.GP3802@adacore.com \
--to=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).