From: Gerald Pfeifer <gerald@pfeifer.com>
To: Jim Meyering <jim@meyering.net>, Mike Stump <mikestump@comcast.net>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] doubled words
Date: Sat, 16 Apr 2011 16:02:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1104161258550.6474@gerinyyl.fvgr> (raw)
In-Reply-To: <892EA220-2EC7-4DAD-9089-73168984DB2A@comcast.net>
On Fri, 15 Apr 2011, Mike Stump wrote:
> I think these are obvious.
Which means that you can commit them without getting explicit approval,
Jim.
Gerald
next prev parent reply other threads:[~2011-04-16 11:05 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 [this message]
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
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=alpine.LNX.2.00.1104161258550.6474@gerinyyl.fvgr \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--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).