From: 0323pin <0323pin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: leftwm: update to 0.3.0
Date: Sun, 08 May 2022 11:20:53 +0200 [thread overview]
Message-ID: <20220508092053.yTwVXXdV0JCM3mCI5M4NeCx7r3GUC2bP5hzLwr8aiP8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36947@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
New comment by 0323pin on void-packages repository
https://github.com/void-linux/void-packages/pull/36947#issuecomment-1120382152
Comment:
> > > This update was not tested according to the PR description, otherwise, lgtm.
> >
> >
> > Does it mean it won't be merged until someone tests to build and run?
>
> It was build tested by CI, now someone only needs to run test it. In 99% of cases, the PR author tests the update.
I'm rather short of time but, if no one else does it within a week or so, I'll kick a build on my laptop.
next prev parent reply other threads:[~2022-05-08 9:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 5:52 [PR PATCH] New package: leftwm-0.3.0 uncomfyhalomacro
2022-05-02 5:59 ` classabbyamp
2022-05-02 6:10 ` [PR PATCH] [Updated] leftwm: update to 0.3.0 uncomfyhalomacro
2022-05-02 6:10 ` uncomfyhalomacro
2022-05-02 6:11 ` uncomfyhalomacro
2022-05-02 6:12 ` uncomfyhalomacro
2022-05-02 6:18 ` 0323pin
2022-05-02 6:20 ` uncomfyhalomacro
2022-05-02 6:24 ` 0323pin
2022-05-07 4:54 ` 0323pin
2022-05-07 5:07 ` uncomfyhalomacro
2022-05-07 5:21 ` 0323pin
2022-05-07 21:58 ` paper42
2022-05-08 6:14 ` 0323pin
2022-05-08 8:54 ` paper42
2022-05-08 9:20 ` 0323pin [this message]
2022-05-08 15:36 ` uncomfyhalomacro
2022-05-08 16:46 ` 0323pin
2022-05-08 19:20 ` 0323pin
2022-05-08 19:26 ` 0323pin
2022-05-08 20:33 ` paper42
2022-05-08 20:33 ` [PR PATCH] [Merged]: " paper42
2022-05-08 20:59 ` 0323pin
2022-05-09 0:30 ` uncomfyhalomacro
2022-10-02 16:33 ` 0323pin
2022-10-02 16:34 ` 0323pin
2022-10-03 3:34 ` uncomfyhalomacro
2022-10-03 7:01 ` 0323pin
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=20220508092053.yTwVXXdV0JCM3mCI5M4NeCx7r3GUC2bP5hzLwr8aiP8@z \
--to=0323pin@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).