From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21282 invoked by alias); 31 Jul 2014 17:23:36 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 32927 Received: (qmail 25903 invoked from network); 31 Jul 2014 17:23:34 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=WjoOb5e+DpVBmmOzLQuqA8QeCo7jBkUlsj3wJe14imc=; b=qWLQ/79LfMJQdR1GE83IvejLXUHQ+d1CqsQrzFoAG079HV3CVPElR6EjT/qh0UYoJ7 B905AyBNSCZzzhixb8BOgSH/Vlkhb5feUTj5HdwqWLHfs7N5CiDwfE1sRqjyCV5FgVXU hgy014QUjd3Rj1JlHWU1tkpd4XNEqGad5hJ+JxqmGUO2v1Zd5T4RCJVgP3kEe+eRpuQ1 JDtws6Y/X1ULfMNOLa2qglk49jqO4kal6Mh6qyOKbdRuwWVGWr7FbcEvVlCCsBlcsuag FfTUeTDzpzUSD/XIvhP+kvuYbHDU6wMvIGq5ek1B8iY8MHRgVHPN5ST3rVjt6jFrz8JS isPg== X-Received: by 10.180.20.40 with SMTP id k8mr18427001wie.54.1406827409793; Thu, 31 Jul 2014 10:23:29 -0700 (PDT) Date: Thu, 31 Jul 2014 18:23:27 +0100 From: Stephane Chazelas To: Peter Stephenson Cc: zsh-workers@zsh.org Subject: Re: $(...) and << Message-ID: <20140731172327.GB28401@chaz.gmail.com> Mail-Followup-To: Peter Stephenson , zsh-workers@zsh.org References: <20140731092711.GA28401@chaz.gmail.com> <140731092023.ZM16680@torch.brasslantern.com> <20140731174208.67f1b392@pwslap01u.europe.root.pri> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140731174208.67f1b392@pwslap01u.europe.root.pri> User-Agent: Mutt/1.5.21 (2010-09-15) 2014-07-31 17:42:08 +0100, Peter Stephenson: [...] > > An issue tracker needs to be part of a larger plan -- we tried using the > > tracker at SourceForge but it didn't work because no one monitors it, so > > it became an issue black hole. At the moment there isn't anyone to take > > that responsibility. > > Yes, exactly. > > A full issue tracker allowing public input is a lot of maintenance work. > In principle it would be less work just to have an internal list of > issues that's basically the result of discussion on this list and can be > published as such. But it's still some work for someone. [...] What about github? Would it really be a lot more work than following this ML? -- Stephane