From: Martin Guy <martinwguy@gmail.com>
To: gdb@sourceware.org
Subject: gdb-* -> gdb-*a links on FTP site? [was Re: binutils-2.20.1a replaced by 2.20.1 and so 2.21.1a?]
Date: Wed, 28 Dec 2011 17:29:00 -0000 [thread overview]
Message-ID: <CAL4-wQrAu4KoFCP990kyqibM-D0vq7Fs6HUk1_-3K1aaYaiPNQ@mail.gmail.com> (raw)
On Sep 1, 2011, at 10:43:20, Tristan Gingold wrote:
> On Aug 31, 2011, at 9:23 PM, Abdoulaye Walsimou GAYE wrote:
>> On 08/30/2011 05:36 PM, Tristan Gingold wrote:
>> This kind of URL change is a serial killer for automatic build system/script already shipped.
>> Is it possible to have simlinks like 'oldername'->'newname'
>> (as for example binutils-2.21.1a.tar.bz2 tarball will actually contain binutils-2.21.1)?
>
>Yes, good idea.
>Done for 2.16 to 2.21.1.
>
>Tristan.
Hi
Could the same scheme of links be implemented on the gdb download site?
As gdb-6.2a.tar.gz unpacks to gdb-6.2/ etc, that would also avoid the
need for extra code everywhere to handle that
cheers & thanks for all the good work
M
next reply other threads:[~2011-12-28 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 17:29 Martin Guy [this message]
2011-12-28 18:01 ` Joel Brobecker
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=CAL4-wQrAu4KoFCP990kyqibM-D0vq7Fs6HUk1_-3K1aaYaiPNQ@mail.gmail.com \
--to=martinwguy@gmail.com \
--cc=gdb@sourceware.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