From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] qmk: update to 1.0.0.
Date: Thu, 20 Jan 2022 01:53:27 +0100 [thread overview]
Message-ID: <20220120005327.qjb8tAKQoQKBEpfwEdRQb3lCAWyvbDii9cMVRkU3YC0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35056@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 244 bytes --]
New review comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/35056#discussion_r788264462
Comment:
I would put this on one line and wrap it at 80 columns, that's what we do for all other packages.
next prev parent reply other threads:[~2022-01-20 0:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 22:44 [PR PATCH] " ifreund
2022-01-14 22:46 ` [PR PATCH] [Updated] " ifreund
2022-01-14 23:16 ` ifreund
2022-01-15 10:36 ` [PR REVIEW] " paper42
2022-01-15 10:36 ` paper42
2022-01-15 10:36 ` paper42
2022-01-15 10:36 ` paper42
2022-01-15 11:28 ` ifreund
2022-01-15 11:28 ` ifreund
2022-01-15 11:30 ` ifreund
2022-01-15 11:31 ` [PR PATCH] [Updated] " ifreund
2022-01-15 11:33 ` ifreund
2022-01-15 11:35 ` ifreund
2022-01-15 12:15 ` [PR PATCH] [Updated] " ifreund
2022-01-15 12:52 ` ifreund
2022-01-15 12:53 ` [PR REVIEW] " ifreund
2022-01-15 12:54 ` ifreund
2022-01-20 0:53 ` [PR REVIEW] " paper42
2022-01-20 0:53 ` paper42 [this message]
2022-01-20 0:53 ` paper42
2022-01-20 15:01 ` [PR PATCH] [Updated] " ifreund
2022-01-20 15:02 ` ifreund
2022-01-20 17:35 ` [PR PATCH] [Updated] " paper42
2022-01-20 17:35 ` [PR PATCH] [Merged]: " paper42
-- strict thread matches above, loose matches on Subject: below --
2021-08-26 11:33 [PR PATCH] " reedts
2021-08-30 18:07 ` [PR REVIEW] " Chocimier
2021-08-30 18:43 ` reedts
2021-08-30 19:30 ` Chocimier
2021-08-30 19:56 ` reedts
2021-08-30 19:57 ` reedts
2021-08-30 20:03 ` Chocimier
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=20220120005327.qjb8tAKQoQKBEpfwEdRQb3lCAWyvbDii9cMVRkU3YC0@z \
--to=paper42@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).