From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Michael Snyder <msnyder@vmware.com>,
Joel Brobecker <brobecker@adacore.com>,
Paul Koning <paul_koning@dell.com>,
Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
Pedro Alves <pedro@codesourcery.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] remove form feeds
Date: Fri, 14 Jan 2011 21:54:00 -0000 [thread overview]
Message-ID: <AANLkTikh4oMDb47PpJ7A0AKFa0Rd=rA3d95yhLimmNJ4@mail.gmail.com> (raw)
In-Reply-To: <m3y66nnolv.fsf@fleche.redhat.com>
On Fri, Jan 14, 2011 at 1:48 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Michael" == Michael Snyder <msnyder@vmware.com> writes:
>
> Michael> Careful what you ask for. ;-)
> Michael> What do y'all think?
>
> I actually like form feeds in the source. I put them into code to
> provide separation between different logical areas.
Ditto.
And very useful in an editor that lets one easily skip to the
next/previous section.
> If other maintainers are strongly opposed, I won't block their removal.
Ditto (reluctantly).
next prev parent reply other threads:[~2011-01-14 21:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 16:09 [RFC] Fix hpux_major_release variable setting Pierre Muller
2011-01-14 16:32 ` Joel Brobecker
2011-01-14 16:59 ` [RFC-v2] " Pierre Muller
2011-01-14 17:58 ` Joel Brobecker
2011-01-14 18:17 ` Pedro Alves
2011-01-14 18:52 ` Pierre Muller
2011-01-14 18:54 ` Michael Snyder
2011-01-14 19:22 ` Paul Koning
2011-01-14 19:52 ` Joel Brobecker
2011-01-14 21:49 ` [RFA] remove form feeds Michael Snyder
2011-01-14 21:51 ` Tom Tromey
2011-01-14 21:54 ` Doug Evans [this message]
2011-01-14 22:31 ` Joel Brobecker
2011-01-14 23:55 ` Michael Snyder
2011-01-15 11:42 ` [RFC-v2] Fix hpux_major_release variable setting Mark Kettenis
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='AANLkTikh4oMDb47PpJ7A0AKFa0Rd=rA3d95yhLimmNJ4@mail.gmail.com' \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=paul_koning@dell.com \
--cc=pedro@codesourcery.com \
--cc=pierre.muller@ics-cnrs.unistra.fr \
--cc=tromey@redhat.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