From: Doug Evans <dje@transmeta.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Dave Brolley <brolley@redhat.com>, cgen@sources.redhat.com
Subject: Re: [patch][rfa]@arch@_cgen_ifld_table
Date: Tue, 11 Feb 2003 21:21:00 -0000 [thread overview]
Message-ID: <15945.26951.42925.711904@casey.transmeta.com> (raw)
In-Reply-To: <20030211154104.B14524@redhat.com>
Frank Ch. Eigler writes:
> Approving your patches seems like an unnecessary formality,
> given your understanding and history. Does someone see a
> need to avoid recognizing brolley within the maintainers list?
Since you're asking ...
Yes and no.
Even maintainers need their patches approved, or at least discussed,
if the change is substantial.
As long as there continues to be the proviso that substantial changes
get discussed on the list first, sure.
I realize that may have been implicit. Just making it explicit.
next prev parent reply other threads:[~2003-02-11 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 20:18 [patch][rfa]@arch@_cgen_ifld_table Dave Brolley
2003-02-11 20:41 ` [patch][rfa]@arch@_cgen_ifld_table Frank Ch. Eigler
2003-02-11 21:21 ` Doug Evans [this message]
2003-02-12 16:56 ` [patch][rfa]@arch@_cgen_ifld_table Frank Ch. Eigler
2003-02-12 22:52 ` [patch][rfa]@arch@_cgen_ifld_table Dave Brolley
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=15945.26951.42925.711904@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=brolley@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=fche@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).