From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: btrfs-progs: update to 5.11
Date: Sat, 20 Mar 2021 00:48:59 +0100 [thread overview]
Message-ID: <20210319234859.QEQbig4h8ZLESpaxw-Bvmt4C251iR3A8xR_-rXKPOb0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29547@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 328 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/29547#issuecomment-803195615
Comment:
> Should I use build option for it? At least x86_64 people will know that it exists and they might want to use it.
I'd rather wait for a request, unless you want to use them yourself?
next prev parent reply other threads:[~2021-03-19 23:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 18:12 [PR PATCH] [WIP] " FollieHiyuki
2021-03-17 18:32 ` [PR PATCH] [Updated] " FollieHiyuki
2021-03-19 17:18 ` FollieHiyuki
2021-03-19 17:25 ` FollieHiyuki
2021-03-19 17:37 ` [PR PATCH] [Updated] " FollieHiyuki
2021-03-19 17:43 ` ericonr
2021-03-19 17:52 ` FollieHiyuki
2021-03-19 17:57 ` FollieHiyuki
2021-03-19 18:15 ` ericonr
2021-03-19 18:30 ` FollieHiyuki
2021-03-19 21:59 ` [PR PATCH] [Updated] " FollieHiyuki
2021-03-19 23:14 ` FollieHiyuki
2021-03-19 23:30 ` FollieHiyuki
2021-03-19 23:36 ` FollieHiyuki
2021-03-19 23:48 ` ericonr [this message]
2021-03-20 0:08 ` [PR PATCH] [Updated] " FollieHiyuki
2021-03-20 0:10 ` FollieHiyuki
2021-03-20 0:11 ` FollieHiyuki
2021-03-20 0:18 ` FollieHiyuki
2021-03-26 23:38 ` [PR PATCH] [Updated] " FollieHiyuki
2021-05-18 7:21 ` FollieHiyuki
2021-06-01 20:55 ` ologantr
2021-06-01 21:04 ` FollieHiyuki
2021-06-01 21:27 ` ologantr
2021-06-01 21:39 ` [PR PATCH] [Updated] " FollieHiyuki
2021-06-01 21:40 ` FollieHiyuki
2021-06-01 21:43 ` [PR PATCH] [Updated] " FollieHiyuki
2021-06-02 4:14 ` [PR PATCH] [Merged]: " ericonr
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=20210319234859.QEQbig4h8ZLESpaxw-Bvmt4C251iR3A8xR_-rXKPOb0@z \
--to=ericonr@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).