From: "宋文武 via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: potentialuser54@postpro.net
Cc: Kei Kebreau <kkebreau@posteo.net>,
44916-done@debbugs.gnu.org, Michael Rohleder <mike@rohleder.de>
Subject: bug#44916: No option to add whisker menu to xfce panel after installing package xfce4-whiskermenu-plugin.
Date: Fri, 25 Aug 2023 18:20:35 +0800 [thread overview]
Message-ID: <87edjr2zkc.fsf@envs.net> (raw)
In-Reply-To: <c17ef989-cbe1-4b77-b70d-5872f66c0a9e@www.fastmail.com> (potentialuser's message of "Sun, 06 Dec 2020 00:29:01 -0500")
potentialuser54@postpro.net writes:
> Hello Kei and Michael,
>
> Thank you for your work. I'm sorry that I lack technical expertise to
> comment on the patch, nor am I able to test it. I'm also not sure
> about if I should send this email or not because I could not provide
> any insights into this issue. Please inform me if you find this email
> annoying.
> Again, thank you for your work!
>
> Regards.
>
> On Sun, Dec 6, 2020, at 00:11, Kei Kebreau wrote:
>> Hello again!
>>
>> If you are able, please take a look at patch #45062 linked below. I've
>> slightly modified Michael's patch and added one of my own to take a shot
>> at solving this issue. If it passes review (or no one says anything for
>> a while), these changes will be applied to Guix proper.
>>
>> The patch is here: https://issues.guix.gnu.org/45062
>>
>> Thanks,
>> Kei
>>
>> Attachments:
>> * signature.asc
Hello, I believe this issue had been fixed (since #45062), closing.
If not feel free to contact me, thanks!
prev parent reply other threads:[~2023-08-25 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 5:05 bug#44916: No option to add whisker menu to xfce panel after installing package xfce4-whiskermenu-plugin potentialuser54
2020-11-28 15:27 ` Michael Rohleder
2020-12-03 16:24 ` Kei Kebreau
2020-12-06 5:11 ` Kei Kebreau
2020-12-06 5:29 ` potentialuser54
2023-08-25 10:20 ` 宋文武 via Bug reports for GNU Guix [this message]
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=87edjr2zkc.fsf@envs.net \
--to=bug-guix@gnu.org \
--cc=44916-done@debbugs.gnu.org \
--cc=iyzsong@envs.net \
--cc=kkebreau@posteo.net \
--cc=mike@rohleder.de \
--cc=potentialuser54@postpro.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.