From: Gerald Pfeifer <gerald@pfeifer.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>,
Mike Stump <mikestump@comcast.net>
Cc: Michael Witten <mfwitten@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/4] Docs: extend.texi: Remove trailing blanks from lines
Date: Wed, 04 May 2011 18:42:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1105041438240.2899@gerinyyl.fvgr> (raw)
In-Reply-To: <F8B929F6-4147-45CF-859B-C864FD196303@comcast.net>
On Wed, 4 May 2011, Joseph S. Myers wrote:
>> I believe we usually don't do whitespace changes just for the sake
>> of cleaning up things.
>>
>> Unless someone else indicates otherwise, I believe this patch is
>> rejected.
> I think we *should* make such formatting cleanups (not just trailing
> whitespace removal, but other changes to match formatting conventions,
> including fixing leading whitespace in C code to use tabs where it doesn't
> as well as more visible changes) - as long as we are agreed on what the
> convention is to follow
Joseph, if you'd like to approave Michael's patch, I explicitly
non-object.
On Wed, 4 May 2011, Mike Stump wrote:
> gcc had that policy for years and years. To return to that, we just
> need a maintainer to approve or pre-approve these changes. :-)
Documentation may be a bit more relaxed, and if you have one doc
maintainer approve and the other abstain that may be more boring
that you might hope for. :-) Unless others strongly disagree, of
course, still got respective area maintainers and global reviewers.
Gerald
next prev parent reply other threads:[~2011-05-04 18:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 1:22 [PATCH 0/4] Docs: extend.texi Michael Witten
2011-04-28 1:30 ` [PATCH 1/4] Docs: extend.texi: Add missing semicolon for consistency Michael Witten
2015-04-08 19:13 ` Gerald Pfeifer
2015-04-12 1:14 ` Michael Witten
2015-04-12 20:22 ` Gerald Pfeifer
2011-04-28 1:34 ` [PATCH 2/4] Docs: extend.texi: Remove trailing blanks from lines Michael Witten
2011-05-03 20:56 ` Gerald Pfeifer
2011-05-04 6:31 ` Michael Witten
2011-05-04 18:05 ` Mike Stump
2011-05-04 18:39 ` Nathan Froyd
2011-05-04 10:13 ` Joseph S. Myers
2011-05-04 18:34 ` Mike Stump
2011-05-04 18:38 ` Joseph S. Myers
2011-05-04 18:42 ` Gerald Pfeifer [this message]
2011-05-04 18:58 ` Joseph S. Myers
2011-05-04 23:57 ` Mike Stump
2011-05-05 0:15 ` Mike Stump
2011-05-05 9:42 ` Richard Guenther
2011-05-05 18:12 ` Michael Witten
2011-04-28 1:36 ` [PATCH 4/4] Docs: extend.texi: Reword and rearrange attribute node introductions Michael Witten
2011-04-28 1:38 ` [PATCH 3/4] Docs: extend.texi: Rearrange nodes; no text was removed or added Michael Witten
2011-05-21 12:24 ` [PATCH 0/4] Docs: extend.texi Michael Witten
2011-06-10 2:06 ` Michael Witten
2011-06-20 17:20 ` Michael Witten
2011-06-23 8:00 ` Michael Witten
2011-06-27 21:18 ` Michael Witten
2011-06-27 21:36 ` Michael Witten
2011-06-30 22:34 ` Michael Witten
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=alpine.LNX.2.00.1105041438240.2899@gerinyyl.fvgr \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=mfwitten@gmail.com \
--cc=mikestump@comcast.net \
/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).