From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Fwd: MODERATE for zsh-announce@zsh.org
Date: Tue, 4 Sep 2018 07:44:20 -0700 [thread overview]
Message-ID: <CAH+w=7YokMF22L6NYUWewmxJvaowfxzZoBL5n-rRZU=NtsoyPw@mail.gmail.com> (raw)
In-Reply-To: <1536069840.16910.ezmlm@zsh.org>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
---------- Forwarded message ----------
From: Baptiste Daroussin <bapt@freebsd.org>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: Zsh List <zsh-announce@zsh.org>
Bcc:
Date: Tue, 4 Sep 2018 15:54:55 +0200
Subject: Re: zsh 5.6 released
On Tue, Sep 04, 2018 at 09:41:52AM +0100, Peter Stephenson wrote:
> (This is on behalf of Daniel Shahaf, in case his announcement email
> doesn't get through.)
>
> Subject: zsh 5.6 released
>
> Version 5.6 of zsh has been released and is available from
> http://www.zsh.org/pub/ . It will shortly also be available from
> Sourceforge: https://sourceforge.net/projects/zsh/files/ .
>
> This is a security release, fixing CVE-2018-0502 and CVE-2018-13259.
> All sites are encouraged to upgrade from 5.5.1 as soon as possible.
>
> See README and NEWS in the source distribution for more information.
Am I the only one having issues with the tarbal not providing any files in
the Doc/help directory, meaning make install provides me with only dead
symlinks
in the runhelp directory?
Best regards,
Bapt
next parent reply other threads:[~2018-09-04 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1536069840.16910.ezmlm@zsh.org>
2018-09-04 14:44 ` Bart Schaefer [this message]
2018-09-05 7:54 ` Baptiste Daroussin
2018-09-05 8:07 ` Peter Stephenson
2018-09-05 10:14 ` Daniel Shahaf
2018-09-05 19:11 ` [PATCH] dist: Generate doc/help/* and doc/help.txt in builddir rather than srcdir Daniel Shahaf
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='CAH+w=7YokMF22L6NYUWewmxJvaowfxzZoBL5n-rRZU=NtsoyPw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--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).