From: "Kaveh Ghazi" <kghazi@mekamail.com>
To: "Jonathan Larmour" <jifl@eCosCentric.com>
Cc: <overseers@gcc.gnu.org>
Subject: Re: Please update the MPFR package in the gcc ftp directory
Date: Tue, 11 Dec 2007 17:51:00 -0000 [thread overview]
Message-ID: <007401c83c1e$591b5cb0$6401a8c0@glap> (raw)
In-Reply-To: <475EB992.10604@eCosCentric.com>
----- Original Message -----
From: "Jonathan Larmour" <jifl@eCosCentric.com>
To: "Kaveh Ghazi" <kghazi@mekamail.com>
Cc: <overseers@gcc.gnu.org>
Sent: Tuesday, December 11, 2007 9:23 AM
Subject: Re: Please update the MPFR package in the gcc ftp directory
> Kaveh Ghazi wrote:
>> Hi Overseers,
>>
>> As per Mark's message here:
>> http://gcc.gnu.org/ml/gcc-patches/2007-12/msg00498.html
>>
>> Would you please update the MPFR package located in
>> ftp://gcc.gnu.org/pub/gcc/infrastructure/ to the latest (version 2.3.0)
>> and delete the old tarball?
>
> Are you sure about deleting the old one? I ask because from the message
> you
> quote, it would imply people should still expect to find old versions
> there. There are already historical versions of other packages in that
> directory, so it's no big deal. But for now I have indeed moved it away.
>
> Let me know if you want the .gz or .zip versions as well.
>
> Jifl
While GCC may support older MPFR's, if someone is going through the trouble
of upgrading, we want to steer them to the latest version. So deleting the
old tarball is appropriate. No need for the .gz or .zip version, bzip-only
is fine.
Thanks for your help.
--Kaveh
prev parent reply other threads:[~2007-12-11 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 8:20 Kaveh Ghazi
2007-12-11 16:24 ` Jonathan Larmour
2007-12-11 17:51 ` Kaveh Ghazi [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='007401c83c1e$591b5cb0$6401a8c0@glap' \
--to=kghazi@mekamail.com \
--cc=jifl@eCosCentric.com \
--cc=overseers@gcc.gnu.org \
/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).