From: Mike Frysinger <vapier@gentoo.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, slauss@resi.at,
Kaz Kojima <kkojima@rr.iij4u.or.jp>
Subject: Re: [patch] fix superh detection in sim/configure
Date: Mon, 29 Jan 2007 16:42:00 -0000 [thread overview]
Message-ID: <200701291142.47678.vapier@gentoo.org> (raw)
In-Reply-To: <20070129121846.GA26115@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 517 bytes --]
On Monday 29 January 2007 07:18, Daniel Jacobowitz wrote:
> On Sun, Jan 28, 2007 at 10:20:02PM -0500, Mike Frysinger wrote:
> > the superh detection in sim/configure ignores pretty much all useful
> > superh targets and that's no fun ... attached patch should fix things up
> > -mike
>
> OK. Do you have write access or should I commit it?
looks like i do; committed ... thanks
> > 2007-01-28 Manuel Lauss <slauss@resi.at>
>
> Extra space between "Lauss" and "<" please.
indeed ... fixed before committing
-mike
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
prev parent reply other threads:[~2007-01-29 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 3:19 Mike Frysinger
2007-01-29 12:18 ` Daniel Jacobowitz
2007-01-29 16:42 ` Mike Frysinger [this message]
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=200701291142.47678.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=kkojima@rr.iij4u.or.jp \
--cc=slauss@resi.at \
/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