Re: [PATCH v2 2/2] doc: specify an 'html' build sub-directory for the htmldocs target

[Jonathan Corbet <corbet@lwn.net>]

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> Hi,
>
> Jonathan Corbet <corbet@lwn.net> writes:
>
>> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>>
>>> Hi Jonathan,
>>>
>>> Jonathan Corbet <corbet@lwn.net> writes:
>>>> I think I'm going to hold off on this one.  As I said before, it would
>>>> have made sense to do things this way when we made the transition.  At
>>>> this point, though, I think the potential for trouble outweighs the
>>>> benefits that would come from moving things around in this way.
>>>
>>> OK.  The potential for troubles would lie with the scripts to deploy the
>>> doc to the web site, I'd guess?  If that's the place we'd expect
>>> problems, I'm happy to be pointed to it and can try adjusting the
>>> scripts for the change.
>>
>> The trouble lies in any number of scripts at any number of sites;
>> calling this an ABI change would be a stretch, but some of the same
>> concerns apply.
>
> Right.  I wouldn't be too concerned with sites other than the main Linux
> documentation site, though?

We can't really take that attitude; breaking users is bad.  There may
(or may not) be any number of companies generating the HTML docs for
internal use, for example; breaking them would be rude at best.

>> Getting the docs build on kernel.org updated would not be a huge
>> problem, I think, but I don't know what else might break.
>>
>> We can reconsider this, but not before the merge window.
>
> Understood.  Thanks for the follow up!  Should I resend when the next
> window opens?

Sure, you can do that.  No guarantees that the benefits of the change
will seem worth the risk at that time, though.

Thanks,

jon