From: Greg Klanderman <email@example.com>
Subject: Re: The HTML archives are updating again
Date: Tue, 06 Apr 2021 10:29:52 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <20210405225330.GA11770@tarpaulin.shahaf.local2> (Daniel Shahaf's message of "Mon, 5 Apr 2021 22:53:30 +0000")
thanks for all your work on this Daniel!! Nice to have that back!
And the bonus new features!
>>>>> On April 5, 2021 Daniel Shahaf <email@example.com> wrote:
> The HTML archives are now again getting updated with new posts:
> Old links should continue to work, including links to attachments.
> Known issues:
> - Messages between last August and yesterday also two Archived-At
> headers, and the URL in the second one just gives an error. The URL
> will no longer be added to new messages.
> - As part of the migration, the X-Seq values for both -users@ and -workers@
> were bumped by 1000. The gaps are 46290→47291 and 25012→26013.
> New bells and whistles:
> - The HTML form of zsh-announce@'s archive.
> - The list of headers rendered in a message page was trimmed, and "Cc"
> was moved up.
> - The threaded view won't flatten threads at some fixed maximum depth.
> - Syntactic sugar for the "linking to a message by X-Seq" functionality:
> - Archived-At headers using the syntactic sugar.
> - The list of years on /mla/index.html will be automatically updated.
> - A "Send me my patches' X-Seq values by return post" bot, hard-wired to
> only respond to Mikael.
> Please report any issues.
> Apologies for the length of the downtime.
> The raw rfc822 archives, available over https:// and rsync://, have been
> continuously available and up-to-date throughout the downtime.
prev parent reply other threads:[~2021-04-06 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 22:53 Daniel Shahaf
2021-04-06 14:29 ` Greg Klanderman [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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 NNTP newsgroup(s).