public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Jim Meyering <jim@meyering.net>
Cc: Mike Stump <mikestump@comcast.net>,
	Gerald Pfeifer <gerald@pfeifer.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] doubled words
Date: Mon, 18 Apr 2011 18:59:00 -0000	[thread overview]
Message-ID: <20110418184659.GG26439@gmx.de> (raw)
In-Reply-To: <8739lf7elo.fsf@rho.meyering.net>

Hi Jim,

* Jim Meyering wrote on Mon, Apr 18, 2011 at 05:40:03PM CEST:
> Mike Stump wrote:
> > On Apr 16, 2011, at 4:04 AM, Gerald Pfeifer wrote:
> >> On Fri, 15 Apr 2011, Mike Stump wrote:
> >>> I think these are obvious.
> >>
> >> Which means that you can commit them without getting explicit approval
> >
> > Well, technically, it means nothing...

> If you hadn't said anything, I would have committed those typo fixes
> by now, based on what I perceived as your review/approval and on my
> reading of this part of http://gcc.gnu.org/svnwrite.html:
> 
>     Free for all
[...]
> If that policy is no longer in effect or does not apply here,
> can you clarify or point to a more up to date policy?

All I know, the policy hasn't changed.  I think there's been a bit of
splitting hairs involved.  There can be times when it is unclear whether
something is obvious or not.  Even when obvious, it can sometimes be
nice not to push forward when somebody is about to merge a big branch,
or even forbidden ("freeze" mode, e.g., to make a release).

Your changes are about as obvious as they can get.  Reviewers will
complain once obviousness-borderline gets visible (or an "obvious"
patch starts breaking a build ;-).  But we should remember that the
obviousness rule also exists so that reviewers don't even _need_ to
take a look; with "is this obvious?", effectively they do again,
eliminating that advantage.

Cheers, (and yes, all IMVHO)
Ralf

  reply	other threads:[~2011-04-18 18:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15  8:23 Jim Meyering
2011-04-15 17:10 ` Mike Stump
2011-04-16 16:02   ` Gerald Pfeifer
2011-04-16 20:15     ` Mike Stump
2011-04-18 15:54       ` Jim Meyering
2011-04-18 18:59         ` Ralf Wildenhues [this message]
2011-04-18 19:03         ` Mike Stump
2011-04-18 19:56         ` Diego Novillo
2011-04-18 21:18           ` Jim Meyering

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=20110418184659.GG26439@gmx.de \
    --to=ralf.wildenhues@gmx.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=jim@meyering.net \
    --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).