From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] Packaging dependencies for wayland in qtile
Date: Tue, 29 Nov 2022 19:35:32 +0100 [thread overview]
Message-ID: <20221129183532.pkKdytVbXjgdHDCB6e8z_jkNuuZpK3gO6Xd2Nhy1E-E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40837@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
New review comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/40837#discussion_r1035131670
Comment:
Don't use `INSTALL.msg` in this manner; use `README.voidlinux` as abby recommended. That's the idiomatic way to document information specifically related to our packaging of the software. `INSTALL.msg` is meant as a last-ditch attempt to convey critical information, mostly about potentially breaking changes, even though these messages show up in an already noisy environment.
next prev parent reply other threads:[~2022-11-29 18:35 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 16:51 [PR PATCH] " brunothedev
2022-11-29 16:58 ` [PR REVIEW] " classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 16:58 ` classabbyamp
2022-11-29 17:02 ` brunothedev
2022-11-29 18:10 ` ahesford
2022-11-29 18:19 ` [PR PATCH] [Updated] " brunothedev
2022-11-29 18:21 ` [PR REVIEW] " brunothedev
2022-11-29 18:35 ` ahesford [this message]
2022-11-29 18:56 ` [PR PATCH] [Updated] " brunothedev
2022-11-29 19:28 ` brunothedev
2022-11-29 20:02 ` brunothedev
2022-11-29 23:22 ` paper42
2022-11-29 23:26 ` [PR REVIEW] " paper42
2022-11-29 23:26 ` paper42
2022-11-29 23:26 ` paper42
2022-11-30 0:43 ` brunothedev
2022-11-30 0:43 ` [PR PATCH] [Closed]: " brunothedev
2022-11-30 0:43 ` brunothedev
2022-11-30 0:45 ` paper42
2022-11-30 0:54 ` brunothedev
2022-11-30 1:13 ` [PR PATCH] [Updated] " brunothedev
2022-11-30 9:47 ` [PR REVIEW] " sgn
2022-11-30 12:37 ` [PR PATCH] [Updated] " brunothedev
2022-11-30 13:29 ` ahesford
2022-11-30 14:18 ` [PR PATCH] [Updated] " brunothedev
2022-12-05 18:51 ` brunothedev
2022-12-05 18:53 ` classabbyamp
2022-12-06 12:51 ` brunothedev
2022-12-23 20:01 ` brunothedev
2022-12-23 20:01 ` [PR PATCH] [Closed]: " brunothedev
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=20221129183532.pkKdytVbXjgdHDCB6e8z_jkNuuZpK3gO6Xd2Nhy1E-E@z \
--to=ahesford@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).