From: "Scott Bambrough" <scottb@netwinder.org>
To: "Michael Snyder" <msnyder@cygnus.com>,
"Mark Kettenis" <kettenis@wins.uva.nl>
Cc: "Philip Blundell" <philb@gnu.org>, <gdb-patches@sources.redhat.com>
Subject: Re: patch for ARM GNU/Linux
Date: Mon, 05 Feb 2001 15:21:00 -0000 [thread overview]
Message-ID: <01f401c08fca$055387e0$LocalHost@netbackup> (raw)
In-Reply-To: <s3in1c07swk.fsf@soliton.wins.uva.nl>
This patch is ok with me.
Scott
----- Original Message -----
From: Mark Kettenis <kettenis@wins.uva.nl>
To: Michael Snyder <msnyder@cygnus.com>
Cc: Philip Blundell <philb@gnu.org>; <gdb-patches@sources.redhat.com>
Sent: Monday, February 05, 2001 3:54 PM
Subject: Re: patch for ARM GNU/Linux
> Michael Snyder <msnyder@cygnus.com> writes:
>
> > Philip Blundell wrote:
> > >
> > > I needed this patch to build the current code on an arm-linux machine.
> >
> > Mark Kettinis should bless this, but it looks ok to me...
>
> Hmm. Looks like the right thing to me, but Scott Bambrough is listed
> as the GNU/Linux ARM native maintainer in MAINTAINERS.
>
> Mark
>
parent reply other threads:[~2001-02-05 15:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <s3in1c07swk.fsf@soliton.wins.uva.nl>]
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='01f401c08fca$055387e0$LocalHost@netbackup' \
--to=scottb@netwinder.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@wins.uva.nl \
--cc=msnyder@cygnus.com \
--cc=philb@gnu.org \
/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