From: Mark Kettenis <kettenis@gnu.org>
To: brobecker@gnat.com
Cc: Peter.Schauer@regent.e-technik.tu-muenchen.de, kevinb@redhat.com,
gdb-patches@sources.redhat.com
Subject: Re: [RFC] Merge aix.mh and aix432.mh ?
Date: Thu, 12 Aug 2004 07:22:00 -0000 [thread overview]
Message-ID: <200408120720.i7C7KvJE021791@juw15.nfra.nl> (raw)
In-Reply-To: <20040812045900.GS25562@gnat.com> (message from Joel Brobecker on Wed, 11 Aug 2004 21:59:00 -0700)
Date: Wed, 11 Aug 2004 21:59:00 -0700
From: Joel Brobecker <brobecker@gnat.com>
aix.mh and aix432.mh (in config/powerpc) are identical, with the
exception of a comment that applies to all versions of AIX. Should
we only keep aix.mh with the extra comment?
Yes please! If you don't hear from Kevin or Peter soom, I'd say, just
go for it. Please also simplify configure.host accordingly.
Mark
next prev parent reply other threads:[~2004-08-12 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 5:24 Joel Brobecker
2004-08-12 7:22 ` Mark Kettenis [this message]
2004-08-12 16:16 ` Kevin Buettner
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=200408120720.i7C7KvJE021791@juw15.nfra.nl \
--to=kettenis@gnu.org \
--cc=Peter.Schauer@regent.e-technik.tu-muenchen.de \
--cc=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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