From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: rdmacm-utils: Missing man pages for cmtime and udpong
Date: Thu, 27 Apr 2017 07:00:18 +0300 [thread overview]
Message-ID: <20170427040018.GY14088@mtr-leonro.local> (raw)
In-Reply-To: <1493198562.3837.2.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]
On Wed, Apr 26, 2017 at 11:22:42AM +0200, Benjamin Drung wrote:
> Am Dienstag, den 25.04.2017, 21:04 +0300 schrieb Leon Romanovsky:
> > On Mon, Apr 24, 2017 at 03:28:30PM +0200, Benjamin Drung wrote:
> > > Hi,
> > >
> > > the rdmacm-utils binaries cmtime and udpong do not have a
> > > corresponding
> > > man page. Please add some since Debian recommends to ship man
> > > pages
> > > for all binaries.
> >
> > Is it requirement or recommendation?
>
> I looked it up. It's considered a bug. The Debian policy says in §12.1:
I understand, I just don't see many volunteers :( to write it.
>
> "Each program, utility, and function should have an associated manual
> page included in the same package. It is suggested that all
> configuration files also have a manual page included as well. Manual
> pages for protocols and other auxiliary things are optional.
>
> If no manual page is available, this is considered as a bug and should
> be reported to the Debian Bug Tracking System (the maintainer of the
> package is allowed to write this bug report themselves, if they so
> desire). Do not close the bug report until a proper man page is
> available."
>
> See https://www.debian.org/doc/debian-policy/ch-docs.html
>
> --
> Benjamin Drung
> System Developer
> Debian & Ubuntu Developer
>
> ProfitBricks GmbH
> Greifswalder Str. 207
> D - 10405 Berlin
>
> Email: benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org
> Web: https://www.profitbricks.com
>
> Sitz der Gesellschaft: Berlin.
> Registergericht: Amtsgericht Charlottenburg, HRB 125506B.
> Geschäftsführer: Achim Weiss.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-04-27 4:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 13:28 rdmacm-utils: Missing man pages for cmtime and udpong Benjamin Drung
[not found] ` <1493040510.17795.3.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-04-25 18:04 ` Leon Romanovsky
[not found] ` <20170425180423.GT14088-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-04-26 9:22 ` Benjamin Drung
[not found] ` <1493198562.3837.2.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-04-27 4:00 ` Leon Romanovsky [this message]
[not found] ` <20170427040018.GY14088-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-04-28 9:08 ` Benjamin Drung
[not found] ` <1493370517.3837.9.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-04-28 14:18 ` Hal Rosenstock
[not found] ` <550f6e6a-931a-0aba-2d54-1ca1b3a44150-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2017-04-30 5:54 ` Leon Romanovsky
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=20170427040018.GY14088@mtr-leonro.local \
--to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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