From: EppurSiMu0ve <EppurSiMu0ve@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: spice-gtk 0.39-1: USB redirection error
Date: Sat, 16 Oct 2021 00:16:46 +0200 [thread overview]
Message-ID: <20211015221646.1ep5LjxxOygZYHf27r82MnzRE888t3hm11BROocQa9c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33548@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
New comment by EppurSiMu0ve on void-packages repository
https://github.com/void-linux/void-packages/issues/33548#issuecomment-944769179
Comment:
Just in case you need that information, my user is these groups: wheel floppy audio video cdrom optical kvm xbuilder libvirt
next prev parent reply other threads:[~2021-10-15 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 1:17 [ISSUE] " EppurSiMu0ve
2021-10-15 22:16 ` EppurSiMu0ve [this message]
2021-10-16 18:49 ` ahesford
2021-10-24 15:47 ` EppurSiMu0ve
2021-10-24 16:53 ` ahesford
2021-10-24 16:53 ` [ISSUE] [CLOSED] " ahesford
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=20211015221646.1ep5LjxxOygZYHf27r82MnzRE888t3hm11BROocQa9c@z \
--to=eppursimu0ve@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).