public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: Jim Meyering <jim@meyering.net>
Cc: 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:03:00 -0000	[thread overview]
Message-ID: <B3800F24-3B1E-4C63-82D7-BD37409BE318@comcast.net> (raw)
In-Reply-To: <8739lf7elo.fsf@rho.meyering.net>

On Apr 18, 2011, at 8:40 AM, Jim Meyering wrote:
> 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?

No.  Doesn't exist.  The webpage isn't maintained with the actual details...   I'd say that, yes, the last bunch is fine to check in, IMHO.  For the lib* and the */ changes, you'd need to break these down and have someone that knows just what to do with each hunk review it.  So, for example, the go changes should go to Ian, and he can say, yes check them in, or more likely, please submit/check them into the master go repo.  The one in gcc is a shadow of the master.

Just ping any patch you don't get approval for once a week, every week, until approved or rejected.

  parent reply	other threads:[~2011-04-18 18:52 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 [this message]
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=B3800F24-3B1E-4C63-82D7-BD37409BE318@comcast.net \
    --to=mikestump@comcast.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=jim@meyering.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).