From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id a661f438 for ; Thu, 19 Sep 2019 01:44:11 +0000 (UTC) Received: (qmail 16923 invoked by alias); 19 Sep 2019 01:44:04 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: List-Unsubscribe: X-Seq: 24265 Received: (qmail 6666 invoked by uid 1010); 19 Sep 2019 01:44:04 -0000 X-Qmail-Scanner-Diagnostics: from mta02.eastlink.ca by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25573. spamassassin: 3.4.2. Clear:RC:0(24.224.136.13):SA:0(-2.6/5.0):. Processed in 3.724572 secs); 19 Sep 2019 01:44:04 -0000 X-Envelope-From: rayandrews@eastlink.ca X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.eastlink.ca designates 24.224.136.13 as permitted sender) X-Authority-Analysis: v=2.3 cv=CfF2G4jl c=1 sm=1 tr=0 a=zv49KfEsxEDzuN5AGO7r0Q==:117 a=zv49KfEsxEDzuN5AGO7r0Q==:17 a=Nz0KCS2TAAAA:8 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=7G7udO3fD5mgOxaTNVgA:9 a=QEXdDO2ut3YA:10 a=ZerVIEu0q4xqpvNG3HNs:22 X-Vade-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudelgdeghecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfgtefuvffnkffpmfdpqfgfvfenuceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpeftrgihucetnhgurhgvfihsuceorhgrhigrnhgurhgvfihssegvrghsthhlihhnkhdrtggrqeenucffohhmrghinhepohhpvghnshhouhhrtggvrdgtohhmnecukfhppedvgedrvddtjedrledtrdduleegnecurfgrrhgrmhepihhnvghtpedvgedrvddtjedrledtrdduleegpdhhvghloheplgduledvrdduieekrddtrddvngdpmhgrihhlfhhrohhmpehrrgihrghnughrvgifshesvggrshhtlhhinhhkrdgtrgdprhgtphhtthhopeiishhhqdhushgvrhhsseiishhhrdhorhhgnecuvehluhhsthgvrhfuihiivgeptd X-Vade-Score: 0 X-Vade-State: 0 X-EL-IP-NOAUTH: 24.207.90.194 Subject: Re: Opensource.com Zsh article To: zsh-users@zsh.org References: <7a681972-e690-a800-306f-182cd686030d@inlv.org> From: Ray Andrews Message-id: <5349aa4a-299f-76dd-01a1-a4e9e99d7191@eastlink.ca> Date: Wed, 18 Sep 2019 18:43:24 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-version: 1.0 In-reply-to: <7a681972-e690-a800-306f-182cd686030d@inlv.org> Content-type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: 8bit Content-language: en-CA 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?