public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
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 19:56:00 -0000	[thread overview]
Message-ID: <BANLkTinJZcR78Z3dYRm3U5DtdOed9TKvmg@mail.gmail.com> (raw)
In-Reply-To: <8739lf7elo.fsf@rho.meyering.net>

On Mon, Apr 18, 2011 at 11:40, Jim Meyering <jim@meyering.net> wrote:
> Mike Stump wrote:
>> On Apr 16, 2011, at 4:04 AM, Gerald Pfeifer <gerald@pfeifer.com> 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...  It only means something if the
>> maintainer agrees with me, which in general we won't know until they
>> weighing.  Any person that checks in under that rule runs the risk of
>> a, no it isn't.  Now, if we had an obviousness maintainer, they could
>> just approve it; we'd only need a wave of a magic wand to get one.
>> :-)
>
> Hi Mike,
> 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
>
>    The following changes can be made by everyone with SVN write access:
>
>    Fixes for obvious typos in ChangeLog files, docs, web pages,
>    comments and similar stuff. Just check in the fix and copy it
>    to gcc-patches. We don't want to get overly anal-retentive about
>    checkin policies.
>
> 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?

It means exactly that.  If the change falls under the obvious rule,
you don't really need a review.  Simply send the patch to gcc-patches,
make sure you haven't broken anything and commit.

Feel free to commit any of the patches in this series of typo fixes
you just posted.


Diego.

  parent reply	other threads:[~2011-04-18 19:04 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
2011-04-18 19:03         ` Mike Stump
2011-04-18 19:56         ` Diego Novillo [this message]
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=BANLkTinJZcR78Z3dYRm3U5DtdOed9TKvmg@mail.gmail.com \
    --to=dnovillo@google.com \
    --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).