Is digest mode working for mailing lists?

2016-07-02 Thread Hal Murray
A few weeks ago, I signed up for bugs and vc in digest mode. I thought I got one message, maybe one each list, but I haven't seen anything since. I see stuff in the archives for vc but the archives for bugs is empty. -- These are my opinions. I hate spam.

Re: memory locking

2016-07-02 Thread Hal Murray
e...@thyrsus.com said: > I'm not sure what the referent of "that" is. The statistics-gathering I've > seen seems to be all about writing line-at-a-time records to various stats > files; I can't see that generating a lot of memory pressure. > If there's somewhere in the code that is allocating mem

Re: memory locking

2016-07-02 Thread Eric S. Raymond
Hal Murray : > ntpd can take a lot of memory if you collect the statistics for who is > talking to you on a busy machine, for example a pool server. It depends on > how busy and how long you want to keep the data. > > Is there any way to turn that off? > > I don't see any mention in the documen

memory locking

2016-07-02 Thread Hal Murray
e...@thyrsus.com said: > BTW, I think I've knocked the mlockall/threads/async bug on the head. I > swiped some code from chrony that does memlocking after telling ntpd it can > have as much memory as it wants - ntpd's worst-case memory requirement ain't > much. I've had that version running contin

Re: Avoiding merge bubbles

2016-07-02 Thread Eric S. Raymond
Hal Murray : > Where should that be documented? I think I set that when you sent out a > similar message a long time ago but I lost it when making a new clone. I'll add a section on merging and rebasing to the Hacking Guide. Since Mark hasn't responded, I also have a bit set to try to write a c

Re: Avoiding merge bubbles

2016-07-02 Thread Hal Murray
e...@thyrsus.com said: >> Is there any way to set things up so --rebase is the default with pull? > Yes. If you look in your .git/config, adding the "rebase = true" line will > set --rebase for all pulls from master. Thanks. Where should that be documented? I think I set that when you sent ou

Re: asciidoc > 8.6.0 is a build requirement

2016-07-02 Thread Eric S. Raymond
Jason Azze : > I started to try every released asciidoc version between 8.4.5 and > 8.6.8 from https://github.com/asciidoc/asciidoc/releases until I found > the version where the error disappeared. 8.6.0 is the winner. Thanks, I've added that to the requirements in INSTALL. -- htt

Re: Avoiding merge bubbles

2016-07-02 Thread Eric S. Raymond
Hal Murray : > Thanks. I hate that crap as much as anybody. > > > git pull --rebase > > I missed the --rebase part. > > Is there any way to set things up so --rebase is the default with pull? Yes. If you look in your .git/config, adding the "rebase = true" line will set --rebase for all pulls

asciidoc > 8.6.0 is a build requirement

2016-07-02 Thread Jason Azze
I've researched the documentation build failure on CentOS 6. It looks like the version of asciidoc (and a2x) is the culprit. CentOS 6.8 has asciidoc version 8.4.5, which includes a2x version 1.0.0. The build on stock CentOS 6.8 fails with: asciidoc: FAILED: ntpd-man.txt.man-tmp: line 6: section

Re: Avoiding merge bubbles

2016-07-02 Thread Hal Murray
Thanks. I hate that crap as much as anybody. > git pull --rebase I missed the --rebase part. Is there any way to set things up so --rebase is the default with pull? Is there any way to recover after I forget? Can we fix the push process to reject pushes if they have that type of comment? (I

Avoiding merge bubbles

2016-07-02 Thread Eric S. Raymond
This is a request for people doing development on a branch, or merges from GitLab. It was prompted by Hal Murray's commit of 2016-07-01 23: "Merge branch 'master' of gitlab.com:NTPsec/ntpsec" which left a bubble in the commit history. To see it, view the repository with gitk; you'll see a bubble