help / color / mirror / code / Atom feed
From: dana <dana@dana.is>
To: "Bart Schaefer" <schaefer@brasslantern.com>,
	"Zsh hackers list" <zsh-workers@zsh.org>
Cc: "Daniel Shahaf" <d.s@daniel.shahaf.name>
Subject: Re: We should get 5.9** out soon
Date: Wed, 30 Mar 2022 19:34:08 -0500	[thread overview]
Message-ID: <2edcc9b8-6877-40d3-b2c1-158fafeed806@www.fastmail.com> (raw)
In-Reply-To: <CAH+w=7YLws5_V21frOYXn52Lv5_vnXxwRSifzZTSrWOupUbjog@mail.gmail.com>

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.

@Daniel, did you want to see us sort out the VCS_Info escaping stuff we
pushed back from 5.8.1? I'm not in a position to steer that myself; if
you're not either we can push it back again.

Is there anything else that anybody would like to see go in (besides
the dedication we discussed off-list)? Any timing considerations?

On Wed 30 Mar 2022, at 11:51, Bart Schaefer wrote:
> ** Or 6.0 or whatever we're calling it.

Does anyone have any strong feelings about 5.9 vs 6.0? I don't.

(Again i've only been loosely paying attention lately, sorry if i've
missed anything)


  reply	other threads:[~2022-03-31  0:36 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 [this message]
2022-03-31  0:48   ` Bart Schaefer
2022-03-31 10:23   ` Peter Stephenson
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

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2edcc9b8-6877-40d3-b2c1-158fafeed806@www.fastmail.com \
    --to=dana@dana.is \
    --cc=d.s@daniel.shahaf.name \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \


* 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).