From: Mark Mitchell <mark@codesourcery.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>,
john@johnrshannon.com, gcc@gcc.gnu.org
Subject: Re: ACATS
Date: Mon, 03 May 2004 20:39:00 -0000 [thread overview]
Message-ID: <4096ADD9.1020107@codesourcery.com> (raw)
In-Reply-To: <874qr21iqv.fsf@egil.codesourcery.com>
> I believe Mark said all maintainers could approve patches for the 3.4
> branch using the "usual rules" - which are a bit fuzzy when it comes
> to non-regression bugfixes, I admit.
If it's not a documentation change and it's not a regression
fix, it needs my OK, unless I've otherwise explicitly
delegated/preapproved it.
> If you want his opinion it is best to cc: him personally.
Indeed. I tend to get somewhat behind on GCC mail, reading it in batch
mode every few days.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
next prev parent reply other threads:[~2004-05-03 20:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 21:14 ACATS Richard Kenner
2004-04-30 1:48 ` ACATS Zack Weinberg
2004-05-03 20:39 ` Mark Mitchell [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-29 20:55 ACATS Richard Kenner
2004-04-29 19:46 ACATS Richard Kenner
2004-04-29 20:46 ` ACATS John R. Shannon
2004-04-29 13:12 ACATS John R. Shannon
2004-04-29 13:44 ` ACATS Dave Korn
2004-04-29 13:55 ` ACATS John R. Shannon
2004-04-29 14:10 ` ACATS Dave Korn
2004-04-29 17:11 ` ACATS John R. Shannon
2004-04-29 18:32 ` ACATS Dave Korn
2004-04-29 18:46 ` ACATS John R. Shannon
2001-12-06 15:12 ACATS Richard Kenner
2001-12-06 15:08 ACATS Richard Kenner
2001-12-06 14:32 ACATS guerby
2001-12-06 15:00 ` ACATS Joseph S. Myers
2001-12-06 15:06 ` ACATS Florian Weimer
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=4096ADD9.1020107@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=john@johnrshannon.com \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=zack@codesourcery.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).