From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-34528-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 16455 invoked by alias); 13 Feb 2015 10:33:59 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 34528
Received: (qmail 9810 invoked from network); 13 Feb 2015 10:33:45 -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,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
	daniel.shahaf.name; h=x-sasl-enc:date:from:to:cc:subject
	:message-id:references:mime-version:content-type:in-reply-to; s=
	mesmtp; bh=patD0iv3qZ0bg9e8MwSwFnpijPo=; b=cg/0u8HokV/2HWl2k4Vs8
	IhCEptCUnlmgfEPt+hp7alXS6IGyXLXye8+2x+oVmOKdNpNPcF11uarjBYpO7hmD
	hyigCxPj/KKL62+yJpR17FpWhyPdADZ8qhlgleAN0pF5Fnu1CknZWKg/wxKLv9x+
	GlTykS2Fp0auELKyOkHKvU=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
	messagingengine.com; h=x-sasl-enc:date:from:to:cc:subject
	:message-id:references:mime-version:content-type:in-reply-to; s=
	smtpout; bh=patD0iv3qZ0bg9e8MwSwFnpijPo=; b=cDSFq5yIub6M5+eZ3TrY
	YE7qfOs99UhS7jSpReu0e4oPxqPaFIKfA3HdemfdxS7bckCWpnUk6yfLmNLlT2dl
	lEYD2rOLVHJ1coyhqyeGirQlfGDwUrsiYMl1zUi9Rqyhh2x5bUr76NKIouy1tSdP
	mw5xbdiMbdytlwp7g+kFZNg=
X-Sasl-enc: qetBSHR8A679pOzcQ13CwU+Sdd8tw3Gr8ntWsk2cUorU 1423823619
Date: Fri, 13 Feb 2015 10:33:37 +0000
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-workers@zsh.org
Subject: Re: 297 all good.
Message-ID: <20150213103337.GC1848@tarsus.local2>
References: <54DD52EB.5010306@eastlink.ca>
 <150212194141.ZM1273@torch.brasslantern.com>
 <CAHYJk3QzAs+XYA2FWfXF01-AkES68tRxwecKoycE_VXg3yS2Mg@mail.gmail.com>
 <54DD829D.9000806@eastlink.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54DD829D.9000806@eastlink.ca>
User-Agent: Mutt/1.5.21 (2010-09-15)

Ray Andrews wrote on Thu, Feb 12, 2015 at 20:50:37 -0800:
> On 02/12/2015 08:09 PM, Mikael Magnusson wrote:
> >On Fri, Feb 13, 2015 at 4:41 AM, Bart Schaefer
> ><schaefer@brasslantern.com> wrote:
> >>On Feb 12,  5:27pm, Ray Andrews wrote:
> >>} (BTW I trust eg: '297' is a unique ID for each build?)
> >>
> >>Sort of.  It's the number of commits since some flag point (the 5.0.7
> >>release, in this case).  So it'll be unique until after the next such
> >>flag point (probably 5.0.8).
> >This also assumes you don't have any local commits. The actually
> >unique identifier for the commit comes after the g at the end. (It's
> >just the first few digits of the commit hash).
> >
> Ok, good to know, I'm just looking for the briefest effective way of
> referring to this build or that build. The 'commitnumber' is nicely
> sequential and simple, so that should do unless I hear different.

Please don't report bare numbers.  Converting a number like '297' to a
form git understands is ambiguous and a little work.  Instead, report a
revision hash, an X-Seq number (in the commit message), or the value of
$ZSH_PATCHLEVEL.

The X-Seq number is unambiguous even if you have local commits on that
branch that aren't upstream.

Thanks,

Daniel