From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Michael Snyder <msnyder@vmware.com>, Eli Zaretskii <eliz@gnu.org>,
"mark.kettenis@xs4all.nl" <mark.kettenis@xs4all.nl>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] more comment cleanups
Date: Mon, 03 Jan 2011 05:06:00 -0000 [thread overview]
Message-ID: <AANLkTim-AA1+9YmBfQ-YMe2WdCrpTqx3BzJcaYRJL_-s@mail.gmail.com> (raw)
In-Reply-To: <20110103043359.GO2396@adacore.com>
On Sun, Jan 2, 2011 at 8:33 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> So what do others think about source lines over 70 columns?
>
> Enforcing a maximum length of 70 characters seems awfully low to me.
> It's fine if someone decides to use 70 characters for his comments,
> of even his code, but I think that 76 or 78 would give better results.
> I even allow myself to go up to 80 when splitting a line makes it
> particularly ugly and hard to read...
>
ChangeLog should be limited to 74 columns:
[hjl@gnu-6 gdb]$ tail gdb/ChangeLog
For older changes see ChangeLog-2009.
Local Variables:
mode: change-log
left-margin: 8
fill-column: 74
version-control: never
coding: utf-8
End:
[hjl@gnu-6 gdb]$
--
H.J.
next prev parent reply other threads:[~2011-01-03 5:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 23:26 Michael Snyder
[not found] ` <201012312312.oBVNC4fc013647@glazunov.sibelius.xs4all.nl>
[not found] ` <AANLkTimc4kNHOfO2B95cyKjN9SN1O_+LQ3O_4FpwZ3rR@mail.gmail.com>
2011-01-01 0:20 ` Michael Snyder
2011-01-01 9:11 ` Eli Zaretskii
2011-01-01 18:26 ` Michael Snyder
2011-01-03 4:43 ` Joel Brobecker
2011-01-03 5:06 ` H.J. Lu [this message]
2011-01-03 7:35 ` Joel Brobecker
2011-01-03 7:56 ` Eli Zaretskii
2011-01-03 8:06 ` Joel Brobecker
2011-01-03 17:45 ` Eli Zaretskii
2011-01-03 19:33 ` Doug Evans
2011-01-03 19:43 ` Eli Zaretskii
2011-01-03 8:05 ` Mark Kettenis
2011-01-03 20:35 ` Michael Snyder
2011-01-03 20:43 ` Eli Zaretskii
2011-01-03 13:00 ` Eli Zaretskii
2011-01-03 16:00 ` Joel Brobecker
2011-01-03 20:37 ` Michael Snyder
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=AANLkTim-AA1+9YmBfQ-YMe2WdCrpTqx3BzJcaYRJL_-s@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=msnyder@vmware.com \
/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