From: Florian Weimer <fw@deneb.enyo.de>
To: Jean-Philippe MENGUAL <jpmengual@debian.org>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: Please remove the memusage.1 manpage
Date: Sun, 19 Apr 2020 20:54:54 +0200 [thread overview]
Message-ID: <875zdvz4ox.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <5689907b-69a6-090a-dfaf-d0e28babf6aa@debian.org> (Jean-Philippe MENGUAL's message of "Sun, 19 Apr 2020 17:24:37 +0200")
* Jean-Philippe MENGUAL:
> This manpage seems not to match to any command now on Linux, at least in
> Debian but not only. Should not the corresponding manpage be removed
> then. Keeping it makes us translate while useless now.
Fedora packages it in glibc-utils:
$ rpm -ql glibc-utils | grep memus
/usr/bin/memusage
/usr/bin/memusagestat
So perhaps this request should be directed at Debian's manpages
package?
next prev parent reply other threads:[~2020-04-19 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 15:24 Please remove the memusage.1 manpage Jean-Philippe MENGUAL
2020-04-19 18:54 ` Florian Weimer [this message]
2020-04-19 22:38 ` Jean-Philippe MENGUAL
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=875zdvz4ox.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=jpmengual@debian.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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