Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: msnyder@vmware.com, hjl.tools@gmail.com, mark.kettenis@xs4all.nl,
	gdb-patches@sourceware.org
Subject: Re: [patch] more comment cleanups
Date: Mon, 03 Jan 2011 13:00:00 -0000	[thread overview]
Message-ID: <E1PZk1B-0000fr-B0@fencepost.gnu.org> (raw)
In-Reply-To: <20110103043359.GO2396@adacore.com> (message from Joel Brobecker	on Mon, 3 Jan 2011 08:33:59 +0400)

> Date: Mon, 3 Jan 2011 08:33:59 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,	"hjl.tools@gmail.com" <hjl.tools@gmail.com>,	"mark.kettenis@xs4all.nl" <mark.kettenis@xs4all.nl>,	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> 
> > 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.

If we go for a higher number and want to enforce it (and I'm not
saying we should), we should try to add a suitable setting to the C
source files (in the local variables section), or maybe provide a
.dir-locals.el file, for the benefit of Emacs users.  Of course, not
everyone uses Emacs.


  parent reply	other threads:[~2011-01-03 13:00 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
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 [this message]
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=E1PZk1B-0000fr-B0@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --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