From: eric vidal <eric@obarun.org>
To: supervision@list.skarnet.org
Subject: Re: [request for review] Port of s6 documentation to mdoc(7)
Date: Sun, 30 Aug 2020 20:10:34 +1100 [thread overview]
Message-ID: <20200830201034.e19b67e197447221f99a7e79@obarun.org> (raw)
In-Reply-To: <877dtgtu1z.fsf@ada>
On Sun, 30 Aug 2020 18:30:16 +1000
Alexis <flexibeast@gmail.com> wrote:
>
> Hi all,
>
> i recently started using 66 instead of runit on Void - thanks to
> @Obarun, @mobinmob and @teldra for their work and help!
You're welcome. Thank at you to use 66.
> Consequently, and further to
> https://www.mail-archive.com/supervision@list.skarnet.org/msg02278.html
> :
>
> > if people like man pages, they should have man pages, so it's
> > been a
> > few years that I have appealed to the community for this ... I
> > want
> > s6 to be accessible, but I figure that if people really wanted
> > man
> > pages, they'd write man pages
>
> i've spent the last couple of weeks porting the s6 documentation
> to mdoc(7) format:
>
> https://github.com/flexibeast/s6-man-pages
>
> since i really want man pages, and much prefer them to HTML for
> system-level software. :-)
>
> i don't consider the current state of the repo to be 'ready' in a
> general sense, but i do feel it's mostly done, and certainly
> amenable to review. i think this might be a good time to give
> myself a short break from working on it, so i can then come back
> and do a review pass with fresher eyes.
>
> The porting has been done manually, with no automation involved;
> this has allowed me to use semantic markup as much as possible,
> which of course also facilitates searching for content with
> `apropos(1)`.
>
> Several things to note:
>
> * i've changed page layouts to fit mdoc(7) conventions.
>
> * During the porting process, i developed ideas about what might
> be the best way to do things, so documentation ported earlier
> might not follow the same style as the documentation ported more
> recently. This is something i hope to check in my review pass.
>
> * There are currently no cross-references to the execline suite or
> skalibs. However, i'm willing to port that documentation as
> well, together with the s6-rc documentation.
>
> * Inline links to things such as djb's software are not yet
> included. The `Lk` macro allows one to supply link text as well
> as the URL, but the resulting output would require changes to
> the text to make it read satisfactorily. Regardless, i can add
> the relevant links in "SEE ALSO" sections.
>
> * i've corrected a number of typos and grammatical issues, and
> discovered what i believe might be couple of errors:
>
> * s6-softlimit: The "Options" section refers to "-r allmem"
> rather than "-r res".
>
> * s6-ftrig-listen: The "Options" section says: "By default,
> s6-ftrig-listen1 waits indefinitely for a matching series of
> events." Given the context, i presume this should be
> "s6-ftrig-listen"?
>
> That said, although i've tried to be careful, i might have
> introduced new errors, or made mistakes in my choice of macros, so
> proofreading would be appreciated. :-)
>
>
> Alexis.
This is really a hard job to do. Many thanks to make it. A lot of user will appreciate it.
Well, i'm not really good at English, so my help will not be usefull about grammatical issues. But i will do some publicizes about your work that be visible by user.
--
eric vidal <eric@obarun.org>
next prev parent reply other threads:[~2020-08-30 9:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 8:30 Alexis
2020-08-30 9:10 ` eric vidal [this message]
2020-08-31 6:56 ` Alexis
2020-08-30 10:01 ` Laurent Bercot
2020-08-31 7:01 ` Alexis
2020-08-31 11:04 ` Laurent Bercot
2020-08-31 14:29 ` Guillermo
2020-09-01 10:00 ` possible s6-rc redesign (was: [request for review] Port of s6 documentation to mdoc(7)) Laurent Bercot
2020-09-01 19:24 ` possible s6-rc redesign mobinmob
2020-09-01 22:16 ` Dudemanguy
2020-09-01 22:20 ` Laurent Bercot
2020-09-02 9:41 ` mobinmob
2020-09-02 12:14 ` Laurent Bercot
2020-09-01 23:14 ` possible s6-rc redesign (was: [request for review] Port of s6 documentation to mdoc(7)) Steve Litt
2020-08-31 16:08 ` [request for review] Port of s6 documentation to mdoc(7) J. Lewis Muir
2020-08-31 17:45 ` Jason Lenz
2020-08-31 19:14 ` J. Lewis Muir
2020-08-31 20:51 ` Laurent Bercot
2020-09-01 6:38 ` Casper Ti. Vector
2020-09-01 9:03 ` Alexis
2020-09-01 9:20 ` Casper Ti. Vector
2020-09-01 10:02 ` Alexis
2020-09-01 10:15 ` Casper Ti. Vector
2020-09-01 20:13 ` Steve Litt
2020-09-02 0:50 ` Alexis
[not found] ` <20200901063801.GA2158@caspervector>
2020-09-01 10:11 ` Laurent Bercot
2020-09-01 11:28 ` Casper Ti. Vector
2020-09-01 11:55 ` Alexis
2020-08-31 19:36 ` Laurent Bercot
2020-08-31 19:58 ` J. Lewis Muir
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=20200830201034.e19b67e197447221f99a7e79@obarun.org \
--to=eric@obarun.org \
--cc=supervision@list.skarnet.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;
as well as URLs for NNTP newsgroup(s).