From: Peter Stephenson <firstname.lastname@example.org>
To: Zsh hackers list <email@example.com>
Subject: Re: We should get 5.9** out soon
Date: Thu, 31 Mar 2022 11:23:49 +0100 (BST) [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
> On 31 March 2022 at 01:34 dana <email@example.com> wrote:
> On Wed 30 Mar 2022, at 11:51, Bart Schaefer wrote:
> > Lots of accumulated fixes, but probably the most important is to
> > un-break line-buffered input (workers/49792), since that problem was
> > introduced by the 5.8.1 security release.
> I'm ready whenever.
That's great, thanks. I agree sooner rather than later is better; I see
Lawrence is chasing some bits and pieces which might prod a few udpates
but none of those looks particularly crucial if they don't.
> Does anyone have any strong feelings about 5.9 vs 6.0? I don't.
Not very strong, but it has been a long time, and definitely worth getting
all and sundry to upgrade, so 6.0 might be a reasonable choice.
next prev parent reply other threads:[~2022-03-31 10:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 16:51 Bart Schaefer
2022-03-31 0:34 ` dana
2022-03-31 0:48 ` Bart Schaefer
2022-03-31 10:23 ` Peter Stephenson [this message]
2022-03-31 10:47 ` Daniel Shahaf
2022-03-31 10:54 ` Axel Beckert
2022-03-31 11:05 ` Peter Stephenson
2022-03-31 23:31 ` Daniel Shahaf
2022-04-02 22:42 ` dana
2022-04-03 16:07 ` Peter Stephenson
2022-04-03 16:39 ` Bart Schaefer
2022-04-03 17:04 ` Branching (was Re: We should get 5.9** out soon) Bart Schaefer
2022-04-03 19:34 ` dana
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).