We discussed this in #ntpsec. For context, I wasn't the original MR
author, but I was very involved in review of the MR, approved it, and
ultimately merged it.
My understanding is that there are two objections here:
1) Changing the default was mixed in with other changes.
2) It is undesirable t
On Sun, Feb 2, 2020 at 7:27 PM Eric S. Raymond via devel
wrote:
> Richard Laager via devel :
> > On 2/2/20 3:44 PM, Jason Azze via devel wrote:
> > > It looks like the --enable-doc waf configuration option was removed in
> > > the commit "Add support for other asciidoc processors". Was there any
Richard Laager via devel :
> On 2/2/20 3:44 PM, Jason Azze via devel wrote:
> > It looks like the --enable-doc waf configuration option was removed in the
> > commit "Add support for other asciidoc processors". Was there any
> > discussion about this change?
>
> Yes. See the mailing list archive
On 2/2/20 6:25 PM, James Browning via devel wrote:
> On Sun, Feb 2, 2020, at 3:49 PM Gary E. Miller via devel
> wrote:
>>
>> Yo Jason!
>>
>> On Sun, 02 Feb 2020 16:44:25 -0500
>> Jason Azze via devel wrote:
>>
>>> It looks like the --enable-doc waf configuration option was removed
>>> in the comm
On Sun, Feb 2, 2020, at 3:49 PM Gary E. Miller via devel
wrote:
>
> Yo Jason!
>
> On Sun, 02 Feb 2020 16:44:25 -0500
> Jason Azze via devel wrote:
>
> > It looks like the --enable-doc waf configuration option was removed
> > in the commit "Add support for other asciidoc processors". Was there
> >
Gary said:
> Not that I saw. I'm for bringing it back. Asciidoctor pulls in ruby, and
> ruby mutates so quickly that I find it often broken.
There was a gigantic discussion, but it was over on MR !1037 rather than here.
The info is in NEWS. It was appended to the Repository head section rat
Yo Jason!
On Sun, 02 Feb 2020 16:44:25 -0500
Jason Azze via devel wrote:
> It looks like the --enable-doc waf configuration option was removed
> in the commit "Add support for other asciidoc processors". Was there
> any discussion about this change?
Not that I saw. I'm for bringing it back. A
On 2/2/20 3:44 PM, Jason Azze via devel wrote:
> It looks like the --enable-doc waf configuration option was removed in the
> commit "Add support for other asciidoc processors". Was there any discussion
> about this change?
Yes. See the mailing list archive and MR !1037.
--
Richard
signatur
It looks like the --enable-doc waf configuration option was removed in the
commit "Add support for other asciidoc processors". Was there any discussion
about this change?
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/d
