From: Bart Schaefer <schaefer@brasslantern.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Should there be a Zsh release for true-color support to adopt earlier?
Date: Tue, 6 Nov 2018 15:46:10 -0800 [thread overview]
Message-ID: <CAH+w=7YmUo8ymY_vPoQru6xEZFT+mE-kZ4vVojw98o4j4c-pyg@mail.gmail.com> (raw)
In-Reply-To: <1541543747.2475810.1568038456.0FCE8467@webmail.messagingengine.com>
On Tue, Nov 6, 2018 at 2:46 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> I don't have an opinion on whether to issue a 5.7. That depends on what
> other changes have been made since 5.6, and I don't have time to review
> 'git log' currently to assess that.
Several more attachtty/subjob/superjob fixes that are probably worth
releasing (if people have actually been running the head checkout to
try them).
next prev parent reply other threads:[~2018-11-06 23:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKc7PVCEmTTMRR0P3kx9ktpLDBYqJ+MRsE77UMLFjonEZAixfA@mail.gmail.com>
2018-10-30 23:41 ` Terminal theme tool – a workaround for lack of 24-bit color in Zsh? Oliver Kiddle
2018-11-01 18:42 ` dana
2018-11-04 1:42 ` PATCH: true colour support Oliver Kiddle
2018-11-04 22:57 ` Oliver Kiddle
2018-11-05 14:36 ` Sebastian Gniazdowski
[not found] ` <46482-1541429525.040210@53iC.Cv7F.M2xE>
2018-11-05 15:48 ` Sebastian Gniazdowski
2018-11-05 16:22 ` Sebastian Gniazdowski
2018-11-06 12:12 ` Sebastian Gniazdowski
2018-11-06 13:37 ` Oliver Kiddle
2018-11-06 21:46 ` Sebastian Gniazdowski
2018-11-06 12:22 ` Should there be a Zsh release for true-color support to adopt earlier? Sebastian Gniazdowski
2018-11-06 22:35 ` Daniel Shahaf
2018-11-06 23:46 ` Bart Schaefer [this message]
2018-11-05 14:03 ` Terminal theme tool – a workaround for lack of 24-bit color in Zsh? Sebastian Gniazdowski
2018-11-15 11:50 ` Jun T
2018-11-15 12:44 ` Peter Stephenson
2018-11-16 7:54 ` Jun T
2018-11-19 8:29 ` Oliver Kiddle
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=7YmUo8ymY_vPoQru6xEZFT+mE-kZ4vVojw98o4j4c-pyg@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=d.s@daniel.shahaf.name \
--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).