From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: 5.0.9 / 5.1 agani (ws Re: Recommend latex surgical gloves)
Date: Thu, 20 Aug 2015 10:25:38 -0700 [thread overview]
Message-ID: <CAH+w=7atmwHxK9EjhFNq7GNpWpHHSS80DxeJ9-FTyVKFJ4CqDA@mail.gmail.com> (raw)
In-Reply-To: <20150820174206.4d0c6e02@pwslap01u.europe.root.pri>
On Thu, Aug 20, 2015 at 9:42 AM, Peter Stephenson
<p.stephenson@samsung.com> wrote:
>
> I'm getting bored with 5.0, since the 0 is a bit pointless, and thinking
> of calling it 5.1 (no third field).
Would this mean we move away from the three-field version numbers
entirely, or would e.g. we do 5.1.1 if there were some small but
urgent fix needed (as there seems nearly always to be, as 5.0.6/7/8
demonstrated)?
> There are some quite useful bits of
> enhanced compatibility here and some quite significant bug fixes.
Yes, a surprising amount of significant progress for a short time.
Several "why didn't we think to do it this way before?" sorts of
updates.
> There's nothing in the README yet about the new paste behaviour, which
> there needs to be --- virtually everyone is going to run into this. (I
> know it's in NEWS but it needs to be very clear.)
Is it worth mentioning how to turn it off, rather than just pointing
to the parameter doc?
> (By the way, in case you're keeping count, in the source tree as a
> whole, including generated docs but ignoring binaries, the score is
> currently:
>
> behaviour: 582
> behavior: 169
Yes, and we could probably do a similar analysis on colour and programme ...
next prev parent reply other threads:[~2015-08-20 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 11:15 Recommend latex surgical gloves ED
2015-08-20 16:42 ` 5.0.9 / 5.1 agani (ws Re: Recommend latex surgical gloves) Peter Stephenson
2015-08-20 17:25 ` Bart Schaefer [this message]
2015-08-21 3:38 ` Mikael Magnusson
2015-09-04 13:44 ` mkdir builtin and $'\0' 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=7atmwHxK9EjhFNq7GNpWpHHSS80DxeJ9-FTyVKFJ4CqDA@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).