From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: auto-cpufreq-2.2.0
Date: Wed, 21 Feb 2024 08:57:22 +0100 [thread overview]
Message-ID: <20240221075722.55D5A21612@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48854@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
New comment by meator on void-packages repository
https://github.com/void-linux/void-packages/pull/48854#issuecomment-1956078277
Comment:
> I wouldn't guard it. I would just have a note in the `README.voidlinux` that the two conflict and should not be run at the same time.
@abenson I don't think many people read or know about the `README.voidlinux` specific documentation. Having a safeguard, although a not "100%" one, could be useful. What do you think?
next prev parent reply other threads:[~2024-02-21 7:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 20:17 [PR PATCH] " meator
2024-02-20 20:32 ` [PR PATCH] [Updated] " meator
2024-02-20 20:48 ` meator
2024-02-20 21:06 ` meator
2024-02-20 21:43 ` meator
2024-02-20 21:53 ` meator
2024-02-20 23:17 ` meator
2024-02-20 23:22 ` meator
2024-02-21 0:17 ` abenson
2024-02-21 5:52 ` [PR REVIEW] " Luciogi
2024-02-21 5:55 ` Luciogi
2024-02-21 7:54 ` meator
2024-02-21 7:56 ` [PR PATCH] [Updated] " meator
2024-02-21 7:57 ` meator [this message]
2024-02-21 8:06 ` meator
2024-02-21 11:38 ` [PR REVIEW] " Luciogi
2024-02-21 11:40 ` Luciogi
2024-02-21 18:40 ` meator
2024-05-09 11:15 ` [PR PATCH] [Updated] " meator
2024-08-08 1:52 ` github-actions
2024-08-22 1:53 ` [PR PATCH] [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=20240221075722.55D5A21612@inbox.vuxu.org \
--to=meator@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).