From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: 3.1.6 status
Date: Fri, 23 Jul 1999 16:37:34 +0200 [thread overview]
Message-ID: <9907231437.AA36783@ibmth.df.unipi.it> (raw)
In-Reply-To: "Vin Shelton"'s message of "23 Jul 1999 10:38:27 DFT." <545hfmvcty4.fsf@dusk1.icd.teradyne.com>
Vin Shelton wrote:
> We've had a lot of patches to -test-2. I would think we should have a
> period of no patches before we release 3.1.6. This period of
> stability ensures that we're all running with the same code. Ideally,
> that period of stability would last several days and no bugs would be
> reported against that release. I would recommend releasing a -test-3
> now with all applied patches. I hope this code would end up being the
> 3.1.6 release, but we won't know unless we're all starting from the
> same page.
The trouble is, that's never going to happen. There are always going to be
patches, and at this stage they're all bug fixes (many of them minor
changes to individual completion functions which I'll accept up to the last
minute, since they're localised). If I apply them, they fix a bug; if I
don't, then the shell still has a bug. If I wait until there are none,
I'll wait forever. That's particularly true of the completion code, for
which there are fiendishly many different things going on; we're never
going to get to a state where last week it was wrong and this week it's
right.
FYI, here are the changes that affect general shell usage and
configuration, excluding completion and documentations changes, which I've
applied since test-2.
* Sven: 7259, 7261: Src/subst.c, Src/Modules/parameter.c,
Doc/Zsh/expn.yo, Completion/Core/_normal,
Completion/Core/_parameters: parameter module provides
local information; used in _parameters; _normal uses
$commands when available.
* Bart: 7230: Src/exec.c: cancd2 didn't free string properly
(or at all, in fact).
* Sven: 7217: Src/exec.c: duplicate function name for scriptname.
* Ollivier: 7209, 7210: configure.in, Etc/MACHINES: Elf and a.out
dynamic loading on FreeBSD (MACHINES entry adapted).
* Tanaka Akira: 7205: Src/Modules/mapfile.c: MS_SYNC was not
defined on SunOS 4.
* pws: 7202: Src/Modules/clone.c: add an extra zero argument
to ioctl() to make three.
Three of those were configuration problems, which only a small number of
users will ever see; one (7259/7261) was a minor addition to the parameters
code; two were simple but necessary local fixes (7217 and 7230). I'm not
convinced that's enough to let the saga drag on. But if there's a general
belief, I can hang on another week (and not any apply any patches to the C
code). Vote now.
--
Peter Stephenson <pws@ibmth.df.unipi.it> Tel: +39 050 844536
WWW: http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy
next prev parent reply other threads:[~1999-07-23 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-23 8:03 Peter Stephenson
1999-07-23 14:38 ` Vin Shelton
1999-07-23 14:37 ` Peter Stephenson [this message]
1999-07-23 18:58 ` Hype (was Re: 3.1.6 status) Bruce Stephens
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=9907231437.AA36783@ibmth.df.unipi.it \
--to=pws@ibmth.df.unipi.it \
--cc=zsh-workers@sunsite.auc.dk \
/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).