From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/rfc] Revised multi-arch process
Date: Wed, 15 May 2002 07:52:00 -0000 [thread overview]
Message-ID: <200205151451.g4FEpvi30379@duracef.shout.net> (raw)
Andrew Cagney writes:
+Since each patch is well defined, and since each change has been tested
+and shows no regressions, the patches are considered @emph{fairly}
+obvious. Such patches do not need approval. Occasional steps in the
+process may be more complicated and less clear. The developer is
+expected to use their judgment and is encouraged to seek advice as
+needed.
Can you add some context that these patches do not need additional
approval for people who are already listed in the MAINTAINERS file.
That is, if Joe Contributor sends us a patch by e-mail, we aren't
automatically going to apply it.
Other than that, this is nice, it makes me want to go multi-arch
something. :)
Michael C
next reply other threads:[~2002-05-15 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 7:52 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-14 23:58 Andrew Cagney
2002-05-15 10:38 ` Eli Zaretskii
2002-05-15 21:48 ` Eli Zaretskii
2002-05-16 11:04 ` Michael Snyder
2002-05-16 12:30 ` Eli Zaretskii
2002-06-01 13:15 ` Andrew Cagney
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=200205151451.g4FEpvi30379@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.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