From: "Frank Ch. Eigler" <fche@redhat.com>
To: Dave Brolley <brolley@redhat.com>, cgen@sources.redhat.com
Subject: Re: [patch][rfa]@arch@_cgen_ifld_table
Date: Tue, 11 Feb 2003 20:41:00 -0000 [thread overview]
Message-ID: <20030211154104.B14524@redhat.com> (raw)
In-Reply-To: <3E495AD1.7070305@redhat.com>; from brolley@redhat.com on Tue, Feb 11, 2003 at 03:19:29PM -0500
Hi -
brolley wrote:
> [...]
> This has been tested on fr30 and on our internal port.
> Seeking approval to commit.
Looks fine to me.
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?
- FChE
next prev parent reply other threads:[~2003-02-11 20:41 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 ` Frank Ch. Eigler [this message]
2003-02-11 21:21 ` [patch][rfa]@arch@_cgen_ifld_table Doug Evans
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=20030211154104.B14524@redhat.com \
--to=fche@redhat.com \
--cc=brolley@redhat.com \
--cc=cgen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).