Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: Ben Elliston <bje@redhat.com>
Cc: binutils@sources.redhat.com, gcc-patches@gcc.gnu.org,
	gdb-patches@sources.redhat.com
Subject: Re: Top-level configure.in patch
Date: Tue, 18 Sep 2001 22:15:00 -0000	[thread overview]
Message-ID: <sibsk7kbgh.fsf@daffy.airs.com> (raw)
In-Reply-To: <15272.5937.195468.61032@scooby.brisbane.redhat.com>

Ben Elliston <bje@redhat.com> writes:

> The ChangeLog entry for this patch ought to provide sufficient
> explanation.  I have tested this with a wide variety of shells.  Okay
> to commit?

Old shells don't support the type builtin.  However, since this code
is only run on a Solaris host, I think it's fine.  I doubt anybody
will do a Canadian Cross from a very old system to a Solaris host.

Ian


  reply	other threads:[~2001-09-18 22:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-18 20:55 Ben Elliston
2001-09-18 22:15 ` Ian Lance Taylor [this message]
2001-09-18 23:00   ` Ben Elliston
2002-06-24  8:08 top-level " Ben Elliston
2002-06-24 10:33 ` DJ Delorie

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=sibsk7kbgh.fsf@daffy.airs.com \
    --to=ian@airs.com \
    --cc=binutils@sources.redhat.com \
    --cc=bje@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@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