Re: Re[2]: The case for changing the documentation syntax

And for comparison's sake, here's Asciidoc renders on github: https://github.com/asciidoctor/asciidoctor/blob/master/README.adoc Other features of the asciidoc/asciidoctor ecosystem are: - Asciidoc is also standardized - https://antora.org/ allows you to build 1 documentation website, from

Re: Re[2]: The case for changing the documentation syntax

Adding my 2 cents here: I write documentation a lot and would like to mention the Asciidoc format, and more specifically asciidoctor ( https://asciidoctor.org/). Asciidoc is a _very_ powerful syntax yet extremely simple to use. Here's a link to their cheat sheet to give you a quick idea of the

Re: Re[2]: Makefile:813: recipe for target 'haproxy' failed

Hi Aleks I have solved the problem, OpenSSL was not recognized TARGET=linux24 USE_OPENSSL=1.1.0g SSL_INC=$STATICLIBSSL/include SSL_LIB=$STATICLIBSSL/lib ADDLIB=-ldl All the best Milenko On 7 January 2018 at 20:25, Aleksandar Lazic wrote: > Zadravo Milenko. > > Please

Re: Re[2]: CI/CD HAProxy

2017-12-15 13:07 GMT+05:00 Aleksandar Lazic : > Hi > > -- Originalnachricht -- > Von: "Илья Шипицин" > An: "Aleksandar Lazic" > Cc: "Olivier Doucet" ; "HAProxy" < > haproxy@formilux.org> > Gesendet:

Re: Re[2]:

On 19 March 2011 10:58, Antony ddj...@mail.ru wrote: Hi all, Actually I asked this question because I saw a lot of times systems that had more than 10Gb of free physical memory and they anyway used swap partition(about 1-5 Mb). I saw that happened on FreeBSD and on Linux, so I thought

Re: Re[2]: FreeBSD Ports: bumping haproxy from v1.2.18 - v1.4.x

Also, changing -devel right now at the same will cause all sorts of support issues as people deal with the migration - not everyone reads the UPDATING file before issuing portupgrade -a. Even a solution should be to mark the haproxy-devel has Moved (see /usr/ports/MOVED) I see in