* 297 all good. @ 2015-02-13 1:27 Ray Andrews 2015-02-13 3:41 ` Bart Schaefer 0 siblings, 1 reply; 8+ messages in thread From: Ray Andrews @ 2015-02-13 1:27 UTC (permalink / raw) To: Zsh hackers list All fixed in '297 (BTW I trust eg: '297' is a unique ID for each build?) ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: 297 all good. 2015-02-13 1:27 297 all good Ray Andrews @ 2015-02-13 3:41 ` Bart Schaefer 2015-02-13 4:09 ` Mikael Magnusson 0 siblings, 1 reply; 8+ messages in thread From: Bart Schaefer @ 2015-02-13 3:41 UTC (permalink / raw) To: Zsh hackers list 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). ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: 297 all good. 2015-02-13 3:41 ` Bart Schaefer @ 2015-02-13 4:09 ` Mikael Magnusson 2015-02-13 4:50 ` Ray Andrews 2015-02-13 8:58 ` Axel Beckert 0 siblings, 2 replies; 8+ messages in thread From: Mikael Magnusson @ 2015-02-13 4:09 UTC (permalink / raw) To: Zsh hackers list 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). -- Mikael Magnusson ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: 297 all good. 2015-02-13 4:09 ` Mikael Magnusson @ 2015-02-13 4:50 ` Ray Andrews 2015-02-13 10:33 ` Daniel Shahaf 2015-02-13 8:58 ` Axel Beckert 1 sibling, 1 reply; 8+ messages in thread From: Ray Andrews @ 2015-02-13 4:50 UTC (permalink / raw) To: zsh-workers 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. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: 297 all good. 2015-02-13 4:50 ` Ray Andrews @ 2015-02-13 10:33 ` Daniel Shahaf 2015-02-13 17:22 ` Ray Andrews 0 siblings, 1 reply; 8+ messages in thread From: Daniel Shahaf @ 2015-02-13 10:33 UTC (permalink / raw) To: Ray Andrews; +Cc: zsh-workers 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: 297 all good. 2015-02-13 10:33 ` Daniel Shahaf @ 2015-02-13 17:22 ` Ray Andrews 0 siblings, 0 replies; 8+ messages in thread From: Ray Andrews @ 2015-02-13 17:22 UTC (permalink / raw) To: Daniel Shahaf; +Cc: zsh-workers On 02/13/2015 02:33 AM, Daniel Shahaf wrote: > 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 Ok. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: 297 all good. 2015-02-13 4:09 ` Mikael Magnusson 2015-02-13 4:50 ` Ray Andrews @ 2015-02-13 8:58 ` Axel Beckert 2015-02-13 10:15 ` Peter Stephenson 1 sibling, 1 reply; 8+ messages in thread From: Axel Beckert @ 2015-02-13 8:58 UTC (permalink / raw) To: zsh-workers Hi, On Fri, Feb 13, 2015 at 05:09:53AM +0100, 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). JFTR: The according git command to get the ID we're talking about is "git describe --tags": ~/zsh/zsh-upstream → git describe --tags zsh-5.0.7-297-g7e6faf7 ~/zsh/zsh-upstream → Kind regards, Axel -- /~\ Plain Text Ribbon Campaign | Axel Beckert \ / Say No to HTML in E-Mail and News | abe@deuxchevaux.org (Mail) X See http://www.nonhtmlmail.org/campaign.html | abe@noone.org (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://abe.noone.org/ (Web) ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: 297 all good. 2015-02-13 8:58 ` Axel Beckert @ 2015-02-13 10:15 ` Peter Stephenson 0 siblings, 0 replies; 8+ messages in thread From: Peter Stephenson @ 2015-02-13 10:15 UTC (permalink / raw) Cc: zsh-workers On Fri, 13 Feb 2015 09:58:56 +0100 Axel Beckert <abe@deuxchevaux.org> wrote: > JFTR: The according git command to get the ID we're talking about is > "git describe --tags": > > ~/zsh/zsh-upstream → git describe --tags > zsh-5.0.7-297-g7e6faf7 > ~/zsh/zsh-upstream → It's also available in $ZSH_PATCHLEVEL --- the unambiguous thing to do is report that. (It's dependent on the same info, though, so still subject to local changes.) pws ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2015-02-13 17:52 UTC | newest] Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2015-02-13 1:27 297 all good Ray Andrews 2015-02-13 3:41 ` Bart Schaefer 2015-02-13 4:09 ` Mikael Magnusson 2015-02-13 4:50 ` Ray Andrews 2015-02-13 10:33 ` Daniel Shahaf 2015-02-13 17:22 ` Ray Andrews 2015-02-13 8:58 ` Axel Beckert 2015-02-13 10:15 ` Peter Stephenson
Code repositories for project(s) associated with this public inbox https://git.vuxu.org/mirror/zsh/ This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).