From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Opensource.com Zsh article
Date: Wed, 18 Sep 2019 18:43:24 -0700 [thread overview]
Message-ID: <5349aa4a-299f-76dd-01a1-a4e9e99d7191@eastlink.ca> (raw)
In-Reply-To: <7a681972-e690-a800-306f-182cd686030d@inlv.org>
On 2019-09-18 3:37 p.m., Martijn Dekker wrote:
>
>> I understand that there's no one left in the cockpit at bash, would
>> that not be a better reason?
>
> What makes you think that? If you read through the bug-bash list it's
> pretty obvious that Chet is still firmly in charge and actively
> developing bash as always. It had a new major 5.0 release fairly
> recently as well, which make it run scripts quite a lot faster.
Chet himself informed me of that. But it seems he's been a one man show
for 26 years! It seems a bit of a fragile situation.
> Apple has plenty of in-house manpower and expertise to take over zsh
> development if the need should ever arise.
How would that work in practice? I mean a 'takeover' wouldn't seem to
be desirable but a contribution of resources might be. Who has the last
word in these things?
next prev parent reply other threads:[~2019-09-19 1:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 22:29 Bart Schaefer
2019-09-18 0:39 ` TJ Luoma
2019-09-18 16:06 ` Ray Andrews
2019-09-18 16:13 ` Jérémie Roquet
2019-09-18 16:37 ` Ray Andrews
2019-09-18 16:54 ` Daniel Shahaf
2019-09-18 17:05 ` Ray Andrews
2019-09-18 17:17 ` Roman Perepelitsa
2019-09-18 19:23 ` Ray Andrews
2019-09-18 22:37 ` Martijn Dekker
2019-09-19 1:43 ` Ray Andrews [this message]
2019-09-19 16:08 ` Daniel Shahaf
2019-09-19 17:32 ` Ray Andrews
2019-09-19 18:04 ` Daniel Shahaf
2019-09-19 19:40 ` Ray Andrews
2019-09-19 22:33 ` Daniel Shahaf
2019-09-19 22:59 ` Bart Schaefer
2019-09-20 0:06 ` Ray Andrews
2019-09-20 1:01 ` TJ Luoma
2019-09-20 3:51 ` Ray Andrews
2019-09-20 13:33 ` Daniel Shahaf
2019-09-20 13:51 ` Ray Andrews
2019-09-20 21:51 ` Bart Schaefer
2019-09-20 22:08 ` Ray Andrews
2019-09-21 8:21 ` Daniel Shahaf
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=5349aa4a-299f-76dd-01a1-a4e9e99d7191@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@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).