gha...@gmail.com said:
> That worked. I was not aware that the tag pull had to be explicit.
Just a plain "git pull" worked for me.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/li
On Sun, Jan 1, 2017 at 2:38 PM, Mark Atwood wrote:
> the tags were pushed. maybe git pull --tags ?
That worked. I was not aware that the tag pull had to be explicit.
Thanks,
--
Sanjeev Gupta
+65 98551208 http://www.linkedin.com/in/ghane
___
the tags were pushed. maybe git pull --tags ?
On Sat, Dec 31, 2016 at 12:25 AM Sanjeev Gupta wrote:
> On Wed, Dec 28, 2016 at 5:58 PM, Eric S. Raymond wrote:
>
> My proposal is that we change this before more water has gone under
> the dam. That is:
>
> 1. VERSION should correspond to the la
On Wed, Dec 28, 2016 at 5:58 PM, Eric S. Raymond wrote:
> My proposal is that we change this before more water has gone under
> the dam. That is:
>
> 1. VERSION should correspond to the last tag, not tne next one.
>
> 2. It should *not* be bumped when we ship 0.9.6 - that will bring it
>into
Sanjeev Gupta :
> Could you do ~ , that way it would lexically sort such that
> 0.9.6~499 is before 0.9.6
It's now "+", not "~", but ought to have the same property.
--
http://www.catb.org/~esr/";>Eric S. Raymond
___
devel mailing list
d
On Wed, Dec 28, 2016 at 5:58 PM, Eric S. Raymond wrote:
> A newbie looking at ntpsec-0.9.6-499 would quite reasonably assume it
> means tick 499 after 0.9.6. It doesn't, because we bump VERSION just
> before release rather than just after.
>
As a newbie, I can confirm that I would expect the sa
Hal Murray :
>
> e...@thyrsus.com said:
> > This is -- , where is the commit count
> > since the last tag.
>
> The tick-this-version idea might be more obvious if you change the - between
> version and tick to a +
Very good point. Change pushed.
--
http://www.catb.org/~esr/";
e...@thyrsus.com said:
> This is -- , where is the commit count
> since the last tag.
The tick-this-version idea might be more obvious if you change the - between
version and tick to a +
--
These are my opinions. I hate spam.
___
devel mailin
I have tried to standardize the way we dump the NTPsec version in a way
that is useful, short, and won't break if we ever have to do
repository surgery on the history. (The last criterion excludes using
the git SHA1 ID.)
So:
esr@snark:~/software/ntp-rescue/ntpsec$ build/main/ntpd/ntpd -V
ntpsec-
