From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] systemd service files
Date: Sat, 14 Aug 2021 02:37:47 +0200 [thread overview]
Message-ID: <20210814003747.LuQBsPjcz28QJ44besqBbez3VUnGH6bdSJNx3RBiqQE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32481@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/32481#issuecomment-898781475
Comment:
It doesn't really take space, so that's fair. My only issue is that it might give an appearance of lax packaging policy and standards, since the files are "useless". I don't think that matters much.
next prev parent reply other threads:[~2021-08-14 0:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 14:18 [ISSUE] " Duncaen
2021-08-14 0:37 ` ericonr [this message]
2022-06-02 2:14 ` github-actions
2022-06-17 2:13 ` [ISSUE] [CLOSED] " github-actions
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=20210814003747.LuQBsPjcz28QJ44besqBbez3VUnGH6bdSJNx3RBiqQE@z \
--to=ericonr@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).