public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: Richard Earnshaw <rearnsha@arm.com>
Cc: Nathan Froyd <froydnj@codesourcery.com>,
	Jeff Law <law@redhat.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] cleanup gcse.c:canon_modify_mem_list
Date: Tue, 05 Apr 2011 18:10:00 -0000	[thread overview]
Message-ID: <7F666054-3383-4100-85CA-5652CBE1333C@comcast.net> (raw)
In-Reply-To: <1302008146.25036.15.camel@e102346-lin.cambridge.arm.com>

On Apr 5, 2011, at 5:55 AM, Richard Earnshaw wrote:
> IMO, rototils are generally pointless.

As a counter point, I like polish and style, in addition to beauty and flexibility.  I'd rather see more style cleanups, more polish cleanups and more beautiful cleanups.  I'd like to see more, not less people doing that work.  I'd like to see more maintainership status give out on that basis.  I like rototils.  This is the mechanism by which we give a uniformity to the code, make it predictable, easier to work, easier to copy from.

  parent reply	other threads:[~2011-04-05 18:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  1:45 Nathan Froyd
2011-04-04 18:01 ` Jeff Law
2011-04-05 11:44   ` Nathan Froyd
2011-04-05 12:22     ` Richard Earnshaw
2011-04-05 12:30       ` Nathan Froyd
2011-04-05 12:55         ` Richard Earnshaw
2011-04-05 13:08           ` Jeff Law
2011-04-05 14:40             ` Richard Earnshaw
2011-04-05 18:10           ` Mike Stump [this message]
2011-04-05 19:18         ` Joseph S. Myers
2011-04-05 19:51           ` Nathan Froyd
2011-04-05 16:19     ` Jeff Law
2011-04-04 15:42 Steven Bosscher
2011-04-04 15:50 ` Nathan Froyd

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=7F666054-3383-4100-85CA-5652CBE1333C@comcast.net \
    --to=mikestump@comcast.net \
    --cc=froydnj@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=rearnsha@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).