From: Ben Elliston <bje@au1.ibm.com>
To: DJ Delorie <dj@redhat.com>
Cc: binutils@sourceware.org, dave.anglin@nrc-cnrc.gc.ca
Subject: Re: Fix for PR 1860
Date: Fri, 31 Mar 2006 03:08:00 -0000 [thread overview]
Message-ID: <20060331023754.GA31847@ozlabs.au.ibm.com> (raw)
In-Reply-To: <200603310232.k2V2WGcg012766@greed.delorie.com>
> Technically acceptable, but please consider that you're changing the
> requirements for more than just binutils. Check with gcc, gdb,
> newlib, and cygwin; if nobody objects, go ahead and commit it.
Whoops -- Alan already approved it and I committed it. I should add
the following extra details that I wrote up in the bug report:
Texinfo 4.2 was released on 1 April 2002.
Texinfo 4.3 was released on 14 November 2002.
Texinfo 4.4 was released in 31 January 2003.
I think that raising the minimum requirement on Texinfo to version
4.4 is quite safe.
Nevertheless, I will follow-up with the other projects.
Ben
prev parent reply other threads:[~2006-03-31 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 2:32 Ben Elliston
2006-03-31 2:37 ` DJ Delorie
2006-03-31 3:08 ` Ben Elliston [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=20060331023754.GA31847@ozlabs.au.ibm.com \
--to=bje@au1.ibm.com \
--cc=binutils@sourceware.org \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=dj@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).