From: "Jun T." <takimoto-j@kba.biglobe.ne.jp>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Mailing list archive broken?
Date: Mon, 29 May 2017 13:06:23 +0900 [thread overview]
Message-ID: <37DB61E8-8DA4-4273-9430-D01016DE2770@kba.biglobe.ne.jp> (raw)
On the zsh-workers list archive top page:
http://www.zsh.org/mla/workers/2017/index.html
at least the following two links are broken:
• 2017/05/26 Re: zsh 5.3.1 crashes on completion (Peter Stephenson)
http://www.zsh.org/mla/workers/2017/msg00829.html
• 2017/05/26 Re: ZSH SSH completion with new Include directive in OpenSSH (Daniel Shahaf)
http://www.zsh.org/mla/workers/2017/msg00830.html
The former should link to workers/41164, but doesn't show message text.
The latter should link to workers/41165, but actually links to
workers/41117.
next reply other threads:[~2017-05-29 4:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 4:06 Jun T. [this message]
2017-05-29 23:52 ` Bart Schaefer
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=37DB61E8-8DA4-4273-9430-D01016DE2770@kba.biglobe.ne.jp \
--to=takimoto-j@kba.biglobe.ne.jp \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).