From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Nicolas Petton <nicolas@petton.fr>, 33393@debbugs.gnu.org
Subject: bug#33393: [gnu.org #1336696] 404 link
Date: Tue, 20 Nov 2018 11:55:34 -0500 [thread overview]
Message-ID: <c236rvofi1.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83tvkbivbh.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 20 Nov 2018 18:10:26 +0200")
Eli Zaretskii wrote:
> I was actually about to suggest something easier: point the readers to
> an address that will never change, such as this:
>
> https://shop.fsf.org/collection/books-docs
Are you sure about "never"? :)
> Of course, if we can arrange for a more focused URL that won't be
> invalidated by bitrot, that would be better.
Emacs can change to any URL for the future, but the old URL is used in
past releases and their announcements, so it would be simplest if it
comes back. It ought to be trivial for the FSF store to set up a
redirect. I will do that today.
next prev parent reply other threads:[~2018-11-20 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-1336696@rt.gnu.org>
[not found] ` <4F069477-F85D-4BDB-B42E-C60F529D3275@mail.umw.edu>
2018-11-15 9:05 ` bug#33393: [gnu.org #1336696] 404 link Therese Godefroy via RT
2018-11-15 16:35 ` Glenn Morris
[not found] ` <rt-4.2.14-7-g171caae-15965-1542299753-1380.1336696-8-0@rt.gnu.org>
2018-11-16 8:18 ` Therese Godefroy via RT
2018-11-20 10:12 ` Nicolas Petton
2018-11-20 16:10 ` Eli Zaretskii
2018-11-20 16:55 ` Glenn Morris [this message]
2018-11-20 16:58 ` Glenn Morris
[not found] ` <rt-4.2.14-7-g171caae-29101-1542730233-443.1336696-8-0@rt.gnu.org>
2018-11-20 17:03 ` Therese Godefroy via RT
2018-11-20 16:52 ` Glenn Morris
2018-11-20 17:41 ` Glenn Morris
2018-11-28 20:06 ` Glenn Morris
2018-11-23 10:10 ` Thérèse Godefroy
2018-11-23 10:22 ` Nicolas Petton
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=c236rvofi1.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=33393@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=nicolas@petton.fr \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.