From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Iain Sandoe <idsandoe@googlemail.com>
Cc: GCC Development <gcc@gcc.gnu.org>, overseers@gcc.gnu.org
Subject: Re: Changes in Mail-list to Web integration.
Date: Mon, 9 Mar 2020 09:56:26 +0000 [thread overview]
Message-ID: <CAH6eHdTuC7NkTGeKjxC_9AXfeh-ow4ExOSc3iAvamWZ3do0z9A@mail.gmail.com> (raw)
In-Reply-To: <1E76E5A3-1D15-4E19-9932-58DC3B62F368@googlemail.com>
On Mon, 9 Mar 2020 at 09:45, Iain Sandoe via Gcc <gcc@gcc.gnu.org> wrote:
> The formatting is not (to me) so much of an issue,
I frequently scanned down the right edge of the page looking for
specific email addresses. That's harder to do when the addresses
aren't right-aligned, but I guess I'll get used to it.
>but the separation of
> days and (for me and some others who commented on irc anyway) the “most
> recent first” presentation is very useful and it would be good to get that
> restored.
Yes, for the gcc-bugs, gcc-cvs and libstdc++-cvs archives having
newest first is maybe not essential, but much, much more convenient.
Also https://gcc.gnu.org/pipermail/gcc-bugs/current/ now redirects to
March-2020/thread.html not March-2020/date.html (which would be closer
to the old behaviour).
And as reported on IRC:
https://gcc.gnu.org/ml/ used to redirect to
https://gcc.gnu.org/lists.html but now goes to
https://gcc.gnu.org/pipermail which gives 403 Forbidden.
https://gcc.gnu.org/lists.html#subscribe doesn't work now. Submitting
a subscription request with that form gives a "403 Forbidden" error.
next prev parent reply other threads:[~2020-03-09 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 9:40 Iain Sandoe
2020-03-09 9:56 ` Jonathan Wakely [this message]
2020-03-09 10:01 ` Jonathan Wakely
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=CAH6eHdTuC7NkTGeKjxC_9AXfeh-ow4ExOSc3iAvamWZ3do0z9A@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=idsandoe@googlemail.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).