Just the “beginning” typo then lgtm.

In D30589#687275, @imp wrote:

I do think the origin setting stuff should be in #keeping_current link instead... and I'd prefer to improve that async to this review.

As per comments.

In D30559#686274, @imp wrote:

In D30559#686269, @asomers wrote:

Wait, what? Do we already have a gitlab instance somewhere?

We publish to gitlab.com

Seems good to go now.

In D30331#683313, @blackend wrote:

In D30331#683208, @ceri wrote:

One other note: the pgpkeys article takes about two hours to build on my (admittedly single-CPU 2GB RAM) machine - is that common and do we need to work around that somehow?

Same here now since we do it right with includes. I just launched a build on my machine (10 years old quad-core) 12 minutes ago and it's still running...
Indeed, we need a solution/workaround.

One other note: the pgpkeys article takes about two hours to build on my (admittedly single-CPU 2GB RAM) machine - is that common and do we need to work around that somehow?

In D30331#682856, @ceri wrote:

In D30331#682854, @dbaio wrote:

Hi.

Testing here and I've seen this detail on articles/contributors.

$ cd documentation
$ make DOC_LANG="en" pdf-books pdf-articles
...
asciidoctor: ERROR: _index.adoc: line 117: include file not found: /usr/home/dbaio/FreeBSD/git/doc/documentation/content/en/articles/contributors/content/en/articles/contributors/contrib-committers.adoc

Ah thanks - we know how to fix that, will update.

In D30331#682854, @dbaio wrote:

Hi.

Testing here and I've seen this detail on articles/contributors.

$ cd documentation
$ make DOC_LANG="en" pdf-books pdf-articles
...
asciidoctor: ERROR: _index.adoc: line 117: include file not found: /usr/home/dbaio/FreeBSD/git/doc/documentation/content/en/articles/contributors/content/en/articles/contributors/contrib-committers.adoc

Other generic nit is that this places its outputs into the content directories, whereas I think they should go into public/ somewhere. Not really clear what the correct structure would be, or if we can rely on public/ existing.

ok - happy. thanks!

In D30330#681160, @debdrup wrote:

In D30330#681159, @ceri wrote:

One last nit, sorry - could you sort these alphabetically, with _limits and _login_class above _nice and _oomprotect after it?

I was thinking about that - but I'll want to sort all of the (name)_ variables alphabetically in that case.

One last nit, sorry - could you sort these alphabetically, with _limits and _login_class above _nice and _oomprotect after it?

PDF version of the handbook used in timeout(1) example.
PR raised to track non-updates.

Take all of dbaio's amendments, except timeout.1