From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: oneko-1.2.5
Date: Sat, 07 May 2022 09:32:37 +0200 [thread overview]
Message-ID: <20220507073237.oxnGpBIzGXqa49psrA_B7Yu8iGqFerQxpWNKWyNjCsk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36622@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 376 bytes --]
New comment by 0x5c on void-packages repository
https://github.com/void-linux/void-packages/pull/36622#issuecomment-1120156117
Comment:
After rebasing to avoid rebuilding most of X and removing the patch, it builds without errors on my computer, and beastie is running after my cursor.
You'll need to rebase when removing the patch, but apart from that it should be fine
next prev parent reply other threads:[~2022-05-07 7:32 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 20:23 [PR PATCH] " wael444
2022-04-11 0:01 ` [PR REVIEW] " tibequadorian
2022-04-11 4:41 ` classabbyamp
2022-04-11 4:41 ` classabbyamp
2022-04-11 4:41 ` classabbyamp
2022-04-11 10:54 ` wael444
2022-04-11 10:54 ` wael444
2022-04-11 10:55 ` wael444
2022-04-11 10:58 ` wael444
2022-04-11 10:59 ` [PR PATCH] [Updated] " wael444
2022-04-11 11:01 ` [PR REVIEW] " wael444
2022-04-11 11:19 ` tibequadorian
2022-04-11 11:21 ` wael444
2022-04-11 11:22 ` [PR PATCH] [Updated] " wael444
2022-04-11 12:29 ` [PR REVIEW] " classabbyamp
2022-04-11 12:30 ` wael444
2022-04-11 12:47 ` [PR PATCH] [Updated] " wael444
2022-04-11 13:11 ` [PR REVIEW] " classabbyamp
2022-04-11 13:46 ` paper42
2022-04-11 13:46 ` paper42
2022-04-11 13:46 ` paper42
2022-04-11 13:47 ` paper42
2022-04-11 13:48 ` paper42
2022-04-11 13:55 ` wael444
2022-04-11 13:57 ` [PR PATCH] [Updated] " wael444
2022-04-11 14:04 ` [PR REVIEW] " paper42
2022-04-11 15:16 ` wael444
2022-04-11 15:17 ` [PR PATCH] [Updated] " wael444
2022-04-11 15:21 ` [PR REVIEW] " classabbyamp
2022-04-11 15:31 ` wael444
2022-04-11 16:38 ` wael444
2022-04-11 18:31 ` 0x5c
2022-04-11 18:34 ` 0x5c
2022-04-11 18:41 ` wael444
2022-04-11 19:08 ` 0x5c
2022-04-11 20:36 ` [PR PATCH] [Updated] " wael444
2022-04-11 20:44 ` wael444
2022-04-11 22:31 ` [PR REVIEW] " 0x5c
2022-04-11 22:34 ` wael444
2022-04-11 22:36 ` [PR PATCH] [Updated] " wael444
2022-04-11 23:26 ` classabbyamp
2022-04-11 23:29 ` wael444
2022-05-07 4:04 ` wael444
2022-05-07 4:24 ` 0x5c
2022-05-07 4:49 ` wael444
2022-05-07 7:32 ` 0x5c [this message]
2022-05-11 16:47 ` [PR PATCH] [Updated] " wael444
2022-05-11 16:51 ` wael444
2022-05-11 19:38 ` 0x5c
2022-05-20 5:46 ` [PR PATCH] [Updated] " wael444
2022-05-26 9:20 ` wael444
2022-05-28 21:16 ` [PR PATCH] [Merged]: " leahneukirchen
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=20220507073237.oxnGpBIzGXqa49psrA_B7Yu8iGqFerQxpWNKWyNjCsk@z \
--to=0x5c@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).