From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: lxd: update and unbreak build
Date: Mon, 03 Feb 2020 08:31:20 +0100 [thread overview]
Message-ID: <20200203073120.gh9KWHXTEXbkr4aV2PUp1ZqIFZUQHVBpDeZOD7RRwL0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18750@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
New comment by ernierasta on void-packages repository
https://github.com/void-linux/void-packages/pull/18750#issuecomment-581275859
Comment:
@CameronNemo can you elaborate on that? There is closed issue about using modules, but maybe we should try to convince upstream to use modules if it would help packaging. We can mention this issue there.
next prev parent reply other threads:[~2020-02-03 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 6:58 [PR PATCH] " voidlinux-github
2020-02-03 7:01 ` voidlinux-github
2020-02-03 7:08 ` voidlinux-github
2020-02-03 7:08 ` voidlinux-github
2020-02-03 7:30 ` voidlinux-github
2020-02-03 7:31 ` voidlinux-github [this message]
2020-02-03 9:16 ` [PR PATCH] [Merged]: " voidlinux-github
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=20200203073120.gh9KWHXTEXbkr4aV2PUp1ZqIFZUQHVBpDeZOD7RRwL0@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).