From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gtk-layer-shell: update to 0.7.0.
Date: Sun, 27 Nov 2022 20:19:19 +0100 [thread overview]
Message-ID: <20221127191919.sarfH04sfvdCyVZEw_MmIV2uG1fY3lQ4b22gTnJmCjA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38316@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 295 bytes --]
New comment by motorto on void-packages repository
https://github.com/void-linux/void-packages/pull/38316#issuecomment-1328320844
Comment:
> Does bumping to 0.8.0 make it any better (or worse)?
Unfortunately it doesn't, the problem seems to be on our side (only happens inside the chroot).
next prev parent reply other threads:[~2022-11-27 19:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 19:29 [PR PATCH] " motorto
2022-07-27 19:34 ` [PR PATCH] [Updated] " motorto
2022-07-27 19:38 ` motorto
2022-07-27 19:44 ` motorto
2022-07-27 20:14 ` [DON'T MERGE] " icp1994
2022-07-27 20:16 ` motorto
2022-09-15 9:06 ` [PR PATCH] [Updated] " motorto
2022-09-15 9:10 ` motorto
2022-10-23 11:52 ` [PR PATCH] [Updated] " motorto
2022-10-23 11:56 ` motorto
2022-10-23 12:03 ` [PR PATCH] [Updated] " motorto
2022-10-23 12:11 ` motorto
2022-10-23 12:13 ` motorto
2022-10-23 12:14 ` motorto
2022-11-25 13:53 ` icp1994
2022-11-27 19:19 ` motorto [this message]
2023-01-14 21:14 ` [PR PATCH] [Updated] " motorto
2023-01-14 21:15 ` motorto
2023-01-14 21:37 ` motorto
2023-01-14 21:37 ` motorto
2023-01-15 9:03 ` motorto
2023-01-15 14:24 ` [PR PATCH] [Updated] " motorto
2023-04-12 20:10 ` gtk-layer-shell: update to 0.8.0 icp1994
2023-06-24 19:09 ` icp1994
2023-06-24 20:54 ` motorto
2023-06-24 20:54 ` [PR PATCH] [Closed]: " motorto
-- strict thread matches above, loose matches on Subject: below --
2022-02-26 13:13 [PR PATCH] gtk-layer-shell: update to 0.7.0 motorto
2022-06-26 2:17 ` 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=20221127191919.sarfH04sfvdCyVZEw_MmIV2uG1fY3lQ4b22gTnJmCjA@z \
--to=motorto@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).