From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4652 invoked by alias); 19 Oct 2017 14:37:47 -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: List-Unsubscribe: X-Seq: 41935 Received: (qmail 25460 invoked by uid 1010); 19 Oct 2017 14:37:47 -0000 X-Qmail-Scanner-Diagnostics: from out4-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(66.111.4.28):SA:0(-2.6/5.0):. Processed in 2.295665 secs); 19 Oct 2017 14:37:47 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: d.s@daniel.shahaf.name X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= daniel.shahaf.name; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=rcX8RZ9qoYItrxNkawn3MilNOVRfo FoBzbIaP72cGC4=; b=oHyjD2x02R/nwuz1cllT5KWAJIQNl7WcYOGC5or/uBdwt O3GA5h/OusxPHqxFTJ5y5DUB3VAIeya63XJRJKLUV6CPpj8fBKh1wAPuuGSDtYin 9+/LqDVhcAUanrtD8bw6HeDwRQ3CHY8mvvKpQm2MOLfPW+Hu66UTzP0oXxLbymQn /aIPK92ygmBX2QNymTYuB+0Jbf6E4vzAyvU8D/5qUJ60JpQpLEswhZ+LHeG9P+CH 2dVfwGCaNSQOVe8noAzIofU3g0ZACfwEq5Qd+WIbn7obnHsrIl27IFVvpq63mB84 DeLQtbqSBn9FebquZTlBE+AObIIGIWiEtcK0VNU/w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=rcX8RZ9qoYItrxNkawn3MilNOVRfo FoBzbIaP72cGC4=; b=nhHiINFj/abUIIMHAJrZDBitdH+G65cy7ixQAUGMR8Hpu xfGcJKThxt1HeP9JIAlDkyWQZyZdQdE2RLrkEudG5Ahv0qzSDhHXo9abepxpqu5T MljvZPCKtA3nbuPA7Fosm62I84t4eCh/w50xnFQk++Q4OLZjhAXGAxEEQr+cQNQi +ctChCTTPkr61RYRrvQsfrTFO7OTU+8Ivw5d0ujEk/E7pYyN/4TvFdAMOnHqZCZE iRZpEPWvCjErAo6DJu012MNQJ9PAuWr+9ccNHyoyrGc6+Zik6pohOOPfsBJP2/+S GrRr+qX3HWcazHUQx/T15DSaJ3mdTjDJ+Ev74fY9A== X-ME-Sender: Date: Thu, 19 Oct 2017 14:37:36 +0000 From: Daniel Shahaf To: zsh-workers@zsh.org Cc: Julien Nicoulaud Subject: Re: GH:zsh-users/zsh-completions. Message-ID: <20171019143736.uzln5hj62tydskkr@tarpaulin.shahaf.local2> References: <7240.1507973844@thecus.kiddle.eu> <6529.1508164192@thecus.kiddle.eu> <20171016161151.6981579c@pwslap01u.europe.root.pri> <20171016164239.533e36fb@pwslap01u.europe.root.pri> <20171016174914.GO31613@andrew.cmu.edu> <21335.1508343802@thecus.kiddle.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <21335.1508343802@thecus.kiddle.eu> User-Agent: NeoMutt/20170113 (1.7.2) [having trouble following everything in this thread; replying to just one section] Oliver Kiddle wrote on Wed, Oct 18, 2017 at 18:23:22 +0200: > What I would prefer is for us to leave zsh completions where they are but > optimise the workflow: > > * Encourage completion contributions in the form of github pull > requests to the zsh-users/zsh mirror. This isn't hard to handle: > add github as an additional remote, fetch refs/remotes/xxxx/pr/*, > cherry-pick and push to the sourceforge master. Note that this is already happening: people sometimes submit pull requests to zsh-users/zsh. Some of us are subscribed to notifications from that repository and handle such pull requests, either by fetching them from github and pushing them to sourceforge as Oliver describes, or by redirecting them to -workers@ for discussion and review. Moreover, we could just as easily have both a github mirror and a gitlab mirror and accept pull requests on both of them; all we need is some maintainers (or this list) to subscribe to pull request notifications from the gitlab mirror, and then to fetch pull requests from gitlab and push them to sourceforge in the same manner as done for github. > * Require no mailing list message for basic completion updates. > * Rethink the need to update ChangeLog on every commit. I think this is a subtly different issue, isn't it? The "post to -workers@" and "update ChangeLog" steps are only visible to the core maintainer who integrates a change; they are not visible to the contributor of the patch or to the end-users who consume it. Cheers, Daniel > I realise that this doesn't solve the problems with how to hatch > completions from zsh-completions.