From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 93 invoked by alias); 13 Jul 2017 16:19:16 -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: 41421 Received: (qmail 21392 invoked from network); 13 Jul 2017 16:19:16 -0000 X-Qmail-Scanner-Diagnostics: from mail-qt0-f181.google.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(209.85.216.181):SA:0(-0.2/5.0):. Processed in 1.63693 secs); 13 Jul 2017 16:19:16 -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=-0.2 required=5.0 tests=RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RCVD_IN_SORBS_SPAM,SPF_PASS, T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.216.181 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=fgQazwH/29jo1mCR69Kb0j10XSqAyzrk4oIzMZ2dP8w=; b=FN+a1Wo5eh3V+ugVMGmp0R+funr+yaJy/SZIHAifaf2V6YixAzQPRcjMzY5FL6MJOz l57Al7b1SI8W/zRjkmUlp5eDnt6oflQafZ4yFYlz65+lPzJyOqTVr43WFkhbUqMe4NqT OY7WR9dDW4ntYJ/4FFe/SEwyQFbeOgodSbC2jwxTOxwZCxc/unhLpw+2AR6Ke1Zq2/iF hZUxmYVZwmeA7kkIGyp835/x+LOuDX980eIJMcxnUNZBh9DUOCvEECPzLzrvBVBz2xVf AbS1ff/0ijTfTTJcYrh1+IgYroCQML8R6wgr2BR3J0EHNngsQyP/xuC4DiLy8xVQq2fU oosA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=fgQazwH/29jo1mCR69Kb0j10XSqAyzrk4oIzMZ2dP8w=; b=BoUdR4IR3OYlUSb04Gtj7fqOZkFBC8Towzxh2b/2JCIXqA+LAWt27UorgYjA3phygM lTfq10rCNlRPvjB2ww6jZLj6zHteP0GWT829qOpTzQkg83boXpaYCVkLk5fvK2koEedY upPUTk2lNVx4WDg4W2BxoAHapad7p6akW5bAk8dCDeSjRxZlDj3NgsPdIWwKD84eQZL/ K0xSzb+9jD03VXoZq76T1If5+u7aJ+U0lMcTJW5t6N/2y/i2RdoBCce0QlqQPFTqTqvS mqNtg3obK7xlTQ7DkRA/xmIyTJLXS4GhdnEspnTR3D/+KL1OPhJDei+RJpwRX2jX9qpf DjEQ== X-Gm-Message-State: AIVw110GmEbk1dlmgyyu9emrE6InpYBYHhOhL937e2rBslIHSQQ1PlVR j6fX6xwsS7WxZe4SfZAQe4bEQ5qMqwsb X-Received: by 10.200.58.65 with SMTP id w59mr5790973qte.136.1499962747883; Thu, 13 Jul 2017 09:19:07 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <8627.1499960570@thecus.kiddle.eu> References: <8627.1499960570@thecus.kiddle.eu> From: Bart Schaefer Date: Thu, 13 Jul 2017 09:19:07 -0700 Message-ID: Subject: Re: PATCH: update git completion through git 2.13.2 To: Zsh workers Content-Type: text/plain; charset="UTF-8" On Thu, Jul 13, 2017 at 8:42 AM, Oliver Kiddle wrote: > update for a few new options So I think we had a bit if discussion about this before, but: Is there any reasonable way for _git to check whether the options/subcommands/etc. it completes are actually supported by the installed version of git ? I'm likely to be running a recently-rebuilt zsh on hosts where git is tracking the version in the OS distribution, which is probably quite a bit behind the bleeding edge.