From: firasuke <firasuke@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Is mmlocate.db.5 intended or just a side effect?
Date: Wed, 30 Dec 2020 21:25:02 +0100 [thread overview]
Message-ID: <20201230202502.3uKRRNzROLOdIIHTnVIJS41gdMiUJ3m5q2lodVR4QrQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27526@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
New comment by firasuke on void-packages repository
https://github.com/void-linux/void-packages/issues/27526#issuecomment-752747434
Comment:
Not really, but I was just wondering why it wasn't `mlocate.db.5`.
Perhaps renaming the original source file from `doc/mlocate.db.5` to `doc/locate.db.5` and then modifying the value of `dist_man_MANS` in `Makefile.in` would remove this side-effect.
next prev parent reply other threads:[~2020-12-30 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 10:20 [ISSUE] " firasuke
2020-12-30 18:31 ` leahneukirchen
2020-12-30 20:25 ` firasuke [this message]
2020-12-30 20:29 ` leahneukirchen
2020-12-30 23:00 ` firasuke
2020-12-30 23:06 ` [ISSUE] [CLOSED] " leahneukirchen
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=20201230202502.3uKRRNzROLOdIIHTnVIJS41gdMiUJ3m5q2lodVR4QrQ@z \
--to=firasuke@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).