From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19972 invoked by alias); 28 Aug 2015 23:32:50 -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: 36320 Received: (qmail 3195 invoked from network); 28 Aug 2015 23:32:48 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=d11NI6nocAgcFqHEWKz/XP/Zwx8=; b=s067ur qlrVQkTIourLWE2NPtZkCBjLJMJj2N5r7JL0YEqEcBYZl+DnKJHN75NdKdK13TH3 xpKrq9Do9awVnBMKA5ySVtJbvcUli+GA0NIMsNEyTc6bAcLQg0axrdyxli/VX3Ho 2hXDrmhJnEvkW9t1TCe7c2XgCnFDOGyUuC6Y8= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=d11NI6nocAgcFqHEWKz/XP/Zwx8=; b=hUI3Y ou3AMPpbadvax1Uk9ZGB1O74uyjKjvvDxXcjithB91sNdkfzrSsw9i9ohMoxQtkU DldZJEuYmeuCeEB045jxA/D30/KLDFpUgUGPw82VoaBBQEt0AmcjHarIdYOfr4Us xiqQGE4cI/qxI9j9EJg+vApj48Bw0k8zF39cP0= X-Sasl-enc: ZFrD40s2nyMlpslqBb8x0tVwmcDktAf6pcMU5a4iQ9Hr 1440804762 Date: Fri, 28 Aug 2015 23:32:40 +0000 From: Daniel Shahaf To: zsh-workers@zsh.org Subject: Re: git oddity with zsh repository Message-ID: <20150828233240.GF1939@tarsus.local2> References: <150827164030.ZM1721@torch.brasslantern.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <150827164030.ZM1721@torch.brasslantern.com> User-Agent: Mutt/1.5.21 (2010-09-15) Bart Schaefer wrote on Thu, Aug 27, 2015 at 16:40:30 -0700: > I get "\#CVSPS.NO.BRANCH" offered as a checkout target (remote head) > when completing after "git checkout". [...] Did one of the updates to > the _git completers cause it to become visible? I don't recall anything related.