From: DJ Delorie <dj@redhat.com>
To: paolo.bonzini@polimi.it
Cc: gcc-patches@gcc.gnu.org, neroden@twcny.rr.com,
gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: [PATCH] Get more stuff compiled for the build machine
Date: Thu, 01 Jul 2004 18:02:00 -0000 [thread overview]
Message-ID: <200407011802.i61I2Bji014844@greed.delorie.com> (raw)
In-Reply-To: <40E3BFD7.4080100@polimi.it> (message from Paolo Bonzini on Thu, 01 Jul 2004 09:40:07 +0200)
> Regtested on a native i686-pc-linux-gnu configuration, and on a
> pseudo-Canadian with build=i686-pc-linux-gnu, host=i386-pc-linux-gnu,
> target=i386-pc-openbsd. In both cases the in-tree makeinfo was always
> used. Ok for mainline and src?
Ok.
prev parent reply other threads:[~2004-07-01 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40DC4524.10905@gcc.gnu.org>
[not found] ` <87acyngzi9.fsf@fleche.redhat.com>
[not found] ` <orisd84rxp.fsf@free.redhat.lsd.ic.unicamp.br>
2004-07-01 7:37 ` Paolo Bonzini
2004-07-01 18:02 ` DJ Delorie [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=200407011802.i61I2Bji014844@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@twcny.rr.com \
--cc=paolo.bonzini@polimi.it \
/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