From: phillip.lord@russet.org.uk (Phillip Lord)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: re-organising Emacs FTP
Date: Mon, 09 Apr 2018 14:23:14 +0100 [thread overview]
Message-ID: <878t9wtsxp.fsf@russet.org.uk> (raw)
In-Reply-To: <jwvk1tg7ex3.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Mon, 09 Apr 2018 08:21:39 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Thoughts?
>
> I don't really have an opinion, but for the liveliness of the
> discussion, I'll propose some alternatives:
>
> - Move all but the latest to a subdirectory `old`.
> - Add a symlink to the latest with a name such that it comes first in
> the list.
> Since the sort is "alphabetical" based on ASCII, there aren't many
> chars that get sorted before "-" so I'm not sure which would be the
> best choice in this regard.
>
> The problem I see with your proposal is that the latest releases as well
> as the `latest` link will still appear last,
Yes, I saw that as a problem. We could perhaps rename "emacs" to
"xemacs", then it will always appear after "latest". What do you think?
I quite like the idea of "old", but it has two problems. First, it means
links will change routinely as new releases appear; while this would at
least be predictable, it might still cause issues. Second, as far as I
can tell, the FTP Upload directives do not have a "move" option, so
practically, this is a pain to achieve.
Having directories would at least reduce the problem, in that the last
would be only a few places down the directory listing. Other
possibilities would be to use "current" rather than "latest". Or, get
the ftp.gnu.org to show symlinks first.
I'd like to have a symlink there anyway, because it would mean the
Windows version of Emacs could notify people when updates are available.
Phil
next prev parent reply other threads:[~2018-04-09 13:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 10:59 re-organising Emacs FTP Phillip Lord
2018-04-09 12:21 ` Stefan Monnier
2018-04-09 13:23 ` Phillip Lord [this message]
2018-04-09 13:53 ` Stefan Monnier
2018-04-09 14:12 ` Nicolas Petton
2018-04-09 14:17 ` Stefan Monnier
2018-04-09 14:58 ` Drew Adams
2018-04-10 2:33 ` Richard Stallman
2018-04-10 8:54 ` Robert Pluim
2018-04-09 15:55 ` Yuri Khan
2018-04-09 16:14 ` Eli Zaretskii
2018-04-10 11:45 ` Phillip Lord
2018-04-09 14:10 ` Nicolas Petton
2018-04-10 11:42 ` Phillip Lord
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878t9wtsxp.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).