From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: mark@codesourcery.com
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [Committed] Use special-purpose hash table to speed up walk_tree
Date: Mon, 18 Oct 2004 14:48:00 -0000 [thread overview]
Message-ID: <10410181449.AA03952@vlsi1.ultra.nyu.edu> (raw)
Yes, but I do have the authority to approve patches. If we had a
no-offline-approval policy, what would have happenned is that Matt would
have posted the patch, and I would have immediately approved it. That's
no different that me approving the patch offline; we would still have
had a broken patch committed to the tree.
I agree. The purpose of posting patches to gcc-patches is indeed to have
many sets of eyes look at it, but many of those are after the patch is
checked in. That's the case whether the patch is one written by somebody
with global write privs, approved on-list, or approved off-list.
next reply other threads:[~2004-10-18 14:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 14:48 Richard Kenner [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-14 23:22 Matt Austern
2004-10-14 23:24 ` Phil Edwards
2004-10-15 0:04 ` Matt Austern
2004-10-16 10:17 ` Jakub Jelinek
2004-10-16 10:37 ` Steven Bosscher
2004-10-17 8:30 ` Mark Mitchell
2004-10-17 10:59 ` Steven Bosscher
2004-10-17 18:45 ` Matt Austern
2004-10-18 4:19 ` Mark Mitchell
2004-10-21 21:25 ` Gerald Pfeifer
2004-10-16 10:42 ` Jakub Jelinek
2004-10-16 11:49 ` Jakub Jelinek
2004-10-16 18:29 ` Matt Austern
2004-10-16 18:35 ` Richard Henderson
2004-10-16 18:37 ` Jakub Jelinek
2004-10-16 18:51 ` Richard Henderson
2004-10-16 19:15 ` Jakub Jelinek
2004-10-17 1:11 ` Richard Henderson
2004-10-16 18:14 ` Matt Austern
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=10410181449.AA03952@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=mark@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).