From: Simon Ruderich <simon@ruderich.org>
To: zsh-workers@zsh.org
Subject: Re: zsh 5.1 released [user]
Date: Fri, 2 Oct 2015 16:08:42 +0200 [thread overview]
Message-ID: <20151002140842.GA5859@ruderich.org> (raw)
In-Reply-To: <20150830201324.309d36b0@ntlworld.com>
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
On Sun, Aug 30, 2015 at 08:13:24PM +0100, Peter Stephenson wrote:
> Version 5.1 of zsh has been released and is available from
>
> http://www.zsh.org/pub/
>
> and will be uploaded to Sourceforge.
>
> [snip]
Hello,
Sorry for being absent so long.
I just updated the website for all zsh releases I missed,
including 5.1.1.
Regards
Simon
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
parent reply other threads:[~2015-10-02 14:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20150830201324.309d36b0@ntlworld.com>]
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=20151002140842.GA5859@ruderich.org \
--to=simon@ruderich.org \
--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).