From: afzal mohammed <afzal.mohd.ma@gmail.com>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Boqun Feng <boqun.feng@gmail.com>,
linux-kernel@vger.kernel.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Will Deacon <will.deacon@arm.com>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Stan Drozd <drozdziak1@gmail.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] doc: memory-barriers: reStructure Text
Date: Fri, 5 Jan 2018 09:22:45 +0530 [thread overview]
Message-ID: <20180105035245.GA6780@afzalpc> (raw)
In-Reply-To: <9DBB839D-975D-4E45-A4E2-A8010A55D361@darmarit.de>
Hi,
On Thu, Jan 04, 2018 at 11:27:55AM +0100, Markus Heiser wrote:
> IMO symlinks are mostly ending in a mess, URLs are never stable.
> There is a
>
> https://www.kernel.org/doc/html/latest/objects.inv
>
> to handle such requirements. Take a look at *intersphinx* :
>
> http://www.sphinx-doc.org/en/stable/ext/intersphinx.html
>
> to see how it works: Each Sphinx HTML build creates a file named objects.inv that
> contains a mapping from object names to URIs relative to the HTML set’s root.
>
> This means articles from external (like lwn articles) has to be recompiled.
> Not perfect, but a first solution.
Thanks for the details.
> I really like them
Initially i was sceptical of rst & once instead of hitting the fly,
hit "make htmldocs" on the keyboard :), and the opinion about it was
changed. It was easy to navigate through various docs & the realized
that various topics (& many) were present (yes, it was there earlier
also, but had to dive inside Documentation & search, while viewing the
toplevel index.html made them standout). It was like earlier you had
to go after docs, but now it was docs coming after you, that is my
opinion.
Later while fighting with memory-barriers.txt, felt that it might be
good for it as well as to be in that company.
And the readability as a text is not hurt as well.
It was thought that rst conversion could be done quickly, but since
this was my first attempt with rst, had to put some effort to get a
not so bad output, even if this patch dies, i am happy to have learnt
rst conversion to some extent.
> > Upon trying to understand memory-barriers.txt, i felt that it might be
> > better to have it in PDF/HTML format, thus attempted to convert it to
> > rst. And i see it not being welcomed, hence shelving the conversion.
>
> I think that's a pity.
When one of the author of the original document objected, i felt it is
better to backoff. But if there is a consensus, i will proceed.
afzal
next prev parent reply other threads:[~2018-01-05 3:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 9:34 [PATCH] doc: memory-barriers: reStructure Text afzal mohammed
2018-01-03 23:48 ` Peter Zijlstra
2018-01-04 3:43 ` afzal mohammed
2018-01-04 1:48 ` Boqun Feng
2018-01-04 3:59 ` afzal mohammed
2018-01-04 10:27 ` Markus Heiser
2018-01-05 3:52 ` afzal mohammed [this message]
2018-01-05 10:22 ` Markus Heiser
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=20180105035245.GA6780@afzalpc \
--to=afzal.mohd.ma@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=drozdziak1@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@kernel.org \
--cc=mingo@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox