From: Ian Jackson <ian.jackson@citrix.com>
To: Andrew Cooper <Andrew.Cooper3@citrix.com>
Cc: Lars Kurth <lars.kurth@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>,
Julien Grall <julien.grall@arm.com>,
Jan Beulich <JBeulich@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH 0/3] docs: User oriented documentation
Date: Wed, 20 Mar 2019 16:43:07 +0000 [thread overview]
Message-ID: <23698.28059.770728.572200@mariner.uk.xensource.com> (raw)
In-Reply-To: <7863e7f2-bcb4-d46b-1188-9a6941fdb135@citrix.com>
Andrew Cooper writes ("Re: [PATCH 0/3] docs: User oriented documentation"):
> It turns out that I mis-interpreted the compatibility note in
> https://www.kernel.org/doc/html/latest/doc-guide/sphinx.html# and
> stretch is probably fine.
OK, good.
Well, I think we could say that to build this documentation you have
to have the relevant tools. sphinx is certainly well-regarded and
this is probably a worthwhile upgrade.
What do the earlier tools do ? Should we print some warning and
disable the build, or will they generate slightly-mangled output, or
what ?
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-03-20 16:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 16:20 [PATCH 0/3] docs: User oriented documentation Andrew Cooper
2019-03-19 16:20 ` [PATCH 1/3] docs/sphinx: Skeleton setup Andrew Cooper
2019-03-19 16:20 ` [PATCH 2/3] docs/rst: Use pandoc to render ReStructuredText Andrew Cooper
2019-03-19 16:20 ` [PATCH 3/3] docs/admin-guide: Boot time microcode loading Andrew Cooper
2019-03-19 16:40 ` Jan Beulich
2019-03-20 11:20 ` [PATCH 0/3] docs: User oriented documentation Wei Liu
2019-03-20 11:23 ` Andrew Cooper
2019-03-20 11:28 ` Wei Liu
2019-03-20 11:35 ` Andrew Cooper
2019-03-20 11:49 ` Ian Jackson
2019-03-20 12:36 ` Andrew Cooper
2019-03-20 16:43 ` Ian Jackson [this message]
2019-03-20 16:47 ` Andrew Cooper
2019-03-20 12:02 ` Wei Liu
2019-03-20 16:49 ` George Dunlap
2019-03-20 16:51 ` Andrew Cooper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23698.28059.770728.572200@mariner.uk.xensource.com \
--to=ian.jackson@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=JBeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=lars.kurth@citrix.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.