On Thu, Mar 07, 2019 at 09:47:18AM +, Peter Maydell wrote:
> On Thu, 7 Mar 2019 at 00:04, Cleber Rosa wrote:
> > But I'm assuming the extended sphinx roles/directives will be used, so
> > the only way to check against future breakage would be to build the
> > docs.
> >
> > Do we have strong po
On Thu, 7 Mar 2019 at 00:04, Cleber Rosa wrote:
> But I'm assuming the extended sphinx roles/directives will be used, so
> the only way to check against future breakage would be to build the
> docs.
>
> Do we have strong position in favor or against putting that into the
> "common" `make check` fl
On Tue, Mar 05, 2019 at 05:21:28PM +, Peter Maydell wrote:
> sphinx-build complains:
>
> docs/cpu-hotplug.rst:67: ERROR: Unexpected indentation.
> docs/cpu-hotplug.rst:69: ERROR: Unexpected indentation.
> docs/cpu-hotplug.rst:74: WARNING: Block quote ends without a blank line;
> unexpected un
On 3/5/19 9:21 AM, Peter Maydell wrote:
> sphinx-build complains:
>
> docs/cpu-hotplug.rst:67: ERROR: Unexpected indentation.
> docs/cpu-hotplug.rst:69: ERROR: Unexpected indentation.
> docs/cpu-hotplug.rst:74: WARNING: Block quote ends without a blank line;
> unexpected unindent.
> docs/cpu-hotp
sphinx-build complains:
docs/cpu-hotplug.rst:67: ERROR: Unexpected indentation.
docs/cpu-hotplug.rst:69: ERROR: Unexpected indentation.
docs/cpu-hotplug.rst:74: WARNING: Block quote ends without a blank line;
unexpected unindent.
docs/cpu-hotplug.rst:75: WARNING: Block quote ends without a blank
