public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Ian Kelling <iank@fsf.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: [Bug Infrastructure/29643] New: Release upload process improvements
Date: Fri, 07 Oct 2022 11:38:19 -0400	[thread overview]
Message-ID: <87v8ovtzft.fsf@fsf.org> (raw)
In-Reply-To: <20221003171003.GL7916@redhat.com>


"Frank Ch. Eigler" <fche@redhat.com> writes:

> Hi -
>
>> [...]  For example, (and I would just open a separate bug for this,
>> but I want to get this off my chest): I notice that the sort order
>> on https://sourceware.org/pub/ is alphabetical instead of version
>> ordering, [...]
>
> The systemwide default indexoptions already include versionsort.
> Where do you see something contrary?  I'm seeing e.g. correct behaviour
> in subdirectories such as https://sourceware.org/pub/gcc/releases/ .

You are right, that is an embarrassing mistake, I chalk it up to working
while tired, thought I noticed something and didn't double check.

  reply	other threads:[~2022-10-07 15:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-02 21:17 mark at klomp dot org
2022-10-03  3:10 ` Ian Kelling
2022-10-03 17:10   ` Frank Ch. Eigler
2022-10-07 15:38     ` Ian Kelling [this message]
2022-10-03  4:08 ` [Bug Infrastructure/29643] " iank at fsf dot org
2022-10-06 17:50 ` mark at klomp dot org
2022-10-12  4:07 ` iank at fsf dot org
2022-12-31 16:14 ` mark at klomp dot org
2023-01-04 11:14   ` Ian Kelling
2023-01-04 11:14 ` iank at fsf dot org
2023-01-10  9:51 ` iank at fsf dot org
2023-01-10 10:04 ` iank at fsf dot org

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=87v8ovtzft.fsf@fsf.org \
    --to=iank@fsf.org \
    --cc=fche@redhat.com \
    --cc=overseers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).