From: Alexis <flexibeast@gmail.com>
To: supervision@list.skarnet.org
Subject: Re: s6-man-pages update
Date: Thu, 10 Sep 2020 00:08:15 +1000 [thread overview]
Message-ID: <87r1rbavqo.fsf@ada> (raw)
In-Reply-To: <em27d5dea1-35d7-40ad-8d7a-ec8e33ea3e57@elzian>
Laurent Bercot <ska-supervision@skarnet.org> writes:
> That downside is simply too big, and also, I don't want to take
> responsibility in the official tarballs for content that I don't
> audit
> myself ... if a distribution has a link
> to get the man pages source, they will use it and will just be
> happy
> that there are man pages.
Fair enough. :-) My thought is, to help distros with packaging, i
can add tags to the s6-man-pages repo to match the corresponding
s6 version on which they were based. So at the completion of this
current process, i could add a 2.9.2.0 tag (assuming that the
current docs on skarnet.org are from the 2.9.2.0 release). Does
that sound reasonable?
(i can put together a package template for Void.)
Alexis.
next prev parent reply other threads:[~2020-09-09 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 4:11 Alexis
2020-09-09 8:19 ` Laurent Bercot
2020-09-09 13:12 ` Alexis
2020-09-09 13:16 ` Érico Nogueira
2020-09-09 13:42 ` Laurent Bercot
2020-09-09 14:08 ` Alexis [this message]
2020-09-09 14:55 ` Laurent Bercot
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=87r1rbavqo.fsf@ada \
--to=flexibeast@gmail.com \
--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).