From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Simon Ser <contact@emersion.fr>
Cc: DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: KMS documentation for userspace
Date: Wed, 19 Jun 2019 23:18:28 +0300 [thread overview]
Message-ID: <87fto5pbvv.fsf@intel.com> (raw)
In-Reply-To: <CAKMK7uH7Twme7kn==ZXeCuC5+uL0RAm9fv2KJui=KATZwLHuqw@mail.gmail.com>
On Wed, 19 Jun 2019, Daniel Vetter <daniel@ffwll.ch> wrote:
> - figure out what to do with the libdrm manpages. Some stuff we really
> want to also document there. But geez nroff. Maybe we need to stuff
> libdrm into the kernel, dunno.
How would people feel about converting libdrm man pages to rst, and
using rst2man in the build? We did that for igt man pages [1]. Looking
at the diff, I think it's plain to see how that could lower the bar for
contributing. And perhaps it would be easier to refactor and move
documentation around too.
I forget, I probably used pandoc or something to do the bulk of the igt
conversion, and added some manual polish on top. I'm not volunteering
for the libdrm man page conversion though. ;)
BR,
Jani.
[1] https://gitlab.freedesktop.org/drm/igt-gpu-tools/commit/cc7387f17ce5750fc640355d94ed60b6936c2d7b
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-06-19 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 19:36 KMS documentation for userspace Simon Ser
2019-06-19 19:53 ` Daniel Vetter
2019-06-19 20:18 ` Jani Nikula [this message]
2019-06-22 10:51 ` Daniel Vetter
2019-06-27 15:02 ` Jani Nikula
2020-06-03 10:03 ` Simon Ser
2019-06-22 9:42 ` Simon Ser
2019-06-22 10:50 ` Daniel Vetter
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=87fto5pbvv.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=contact@emersion.fr \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox