Re: Repository surgery is complete

2017-03-20 Thread Fred Wright
On Mon, 20 Mar 2017, Jason Azze wrote: > On Mon, Mar 6, 2017 at 3:41 PM, Eric S. Raymond wrote: > > The NTPsec repo is open for commits again. > > > [snip] > > > > If you have any difficulties with the alterered repo, please report them. > > I created a GitLab fork of the project before the sur

Re: Repository surgery is complete

2017-03-20 Thread Achim Gratz
Eric S. Raymond writes: > 6. Delete and recreate cryptographically-signed tags. Has this happened? I am asking because of this: ~/ntpsec $ git describe git-conversion-4174-g253fdd8 Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ

Re: Repository surgery is complete

2017-03-20 Thread Eric S. Raymond
Jason Azze : > On Mon, Mar 6, 2017 at 3:41 PM, Eric S. Raymond wrote: > > The NTPsec repo is open for commits again. > > > [snip] > > > > If you have any difficulties with the alterered repo, please report them. > > I created a GitLab fork of the project before the surgery, which I > used for gen

Re: Repository surgery is complete

2017-03-20 Thread Jason Azze
On Mon, Mar 6, 2017 at 3:41 PM, Eric S. Raymond wrote: > The NTPsec repo is open for commits again. > [snip] > > If you have any difficulties with the alterered repo, please report them. I created a GitLab fork of the project before the surgery, which I used for generating merge requests. I just

Re: Repository surgery is complete

2017-03-07 Thread Gary E. Miller
Yo Achim! On Tue, 07 Mar 2017 19:49:08 +0100 Achim Gratz wrote: > Gary E. Miller writes: > > NTF === Network Time Foundation. > > > > http://nwtime.org/ > > > > Easier than typing NTP Classic. > > To me NTF means noise transfer function. :-) Narcotics Task Force National Teaching

Re: Repository surgery is complete

2017-03-07 Thread Eric S. Raymond
Achim Gratz : > Eric S. Raymond writes: > > That is correct. I expect the end product to be an ntf-stable branch > > proceeding from the fork point. > > That's the second time (I think) you talk about ntf or NTF > w.r.t. classic NTP branch… is that just a typo for NTP or does it mean > something e

Re: Repository surgery is complete

2017-03-07 Thread Achim Gratz
Gary E. Miller writes: > NTF === Network Time Foundation. > > http://nwtime.org/ > > Easier than typing NTP Classic. To me NTF means noise transfer function. :-) Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http

Re: Repository surgery is complete

2017-03-07 Thread Gary E. Miller
Yo Achim! On Tue, 07 Mar 2017 19:07:36 +0100 Achim Gratz wrote: > That's the second time (I think) you talk about ntf or NTF > w.r.t. classic NTP branch… is that just a typo for NTP or does it mean > something else? NTF === Network Time Foundation. http://nwtime.org/ Easier than typing NTP C

Re: Repository surgery is complete

2017-03-07 Thread Achim Gratz
Eric S. Raymond writes: > That is correct. I expect the end product to be an ntf-stable branch > proceeding from the fork point. That's the second time (I think) you talk about ntf or NTF w.r.t. classic NTP branch… is that just a typo for NTP or does it mean something else? Regards, Achim. -- +

Re: Repository surgery is complete

2017-03-07 Thread Eric S. Raymond
Hal Murray : > > If you have any difficulties with the alterered repo, please report them. > > I did a git pull and all seemed happy. Actually, I did two, one for my local > unaltered copy of gitlab and a second from there to my working copy which had > some changes. Both seemed happy. > > Is

Re: Repository surgery is complete

2017-03-06 Thread Hal Murray
> If you have any difficulties with the alterered repo, please report them. I did a git pull and all seemed happy. Actually, I did two, one for my local unaltered copy of gitlab and a second from there to my working copy which had some changes. Both seemed happy. Is that what you expect? Wil

Repository surgery is complete

2017-03-06 Thread Eric S. Raymond
The NTPsec repo is open for commits again. The surgery seemed to go without a hitch. And yes, the issue tracker *did* resychronize to the new state of the repo. For the record, here's how you do this sort of thing. 1. Pull from the repo. 2. Make local changes with reposurgeon. 3. Go to the re