From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pve-devel] [RFC zfsonlinux 0/5] update to 2.1.1
Date: Wed, 8 Sep 2021 14:25:06 +0200 [thread overview]
Message-ID: <671afce4-d8b6-0870-5d42-8c40bb0aa3d3@proxmox.com> (raw)
In-Reply-To: <1631101918.e108vbagbz.astroid@nora.none>
On 08.09.21 13:53, Fabian Grünbichler wrote:
> On September 7, 2021 3:17 pm, Stoiko Ivanov wrote:
>> This patchset updates our packaging for the changes of ZFS 2.1
>>
>> Sending as RFC because:
>> * I'm still not 100% sure my solution to the ABI-changes and updated
>> package names is correct
>> * It's based on the current tip of upstream's zfs-2.1.1-staging branch,
>> which yet needs to be tagged
>
> I think I'd wait for the final 2.1.1 tag to prevent confusion unless we
> have a good reason to go ahead with an in-between codebase?
>
+1
I may have been a cause of this by telling Stoiko by mentioning that there was
some recent activity in the 2.1.1 staging branch, and that we may want to wait
out for - the intention for mentioning that may have got lost on the way.
prev parent reply other threads:[~2021-09-08 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 13:17 Stoiko Ivanov
2021-09-07 13:17 ` [pve-devel] [RFC zfsonlinux 1/5] update submodule and patches to ZFS 2.1.1-staging Stoiko Ivanov
2021-09-07 13:17 ` [pve-devel] [RFC zfsonlinux 2/5] buildsys: adapt install paths for zfs 2.1.0 Stoiko Ivanov
2021-09-07 13:17 ` [pve-devel] [RFC zfsonlinux 3/5] port changes to abi tracking from master Stoiko Ivanov
2021-09-07 13:17 ` [pve-devel] [RFC zfsonlinux 4/5] update abi definitions for 2.1.1 Stoiko Ivanov
2021-09-07 13:17 ` [pve-devel] [RFC zfsonlinux 5/5] bump libzpool soname Stoiko Ivanov
2021-09-08 11:51 ` Fabian Grünbichler
2021-09-08 11:53 ` [pve-devel] [RFC zfsonlinux 0/5] update to 2.1.1 Fabian Grünbichler
2021-09-08 12:25 ` Thomas Lamprecht [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=671afce4-d8b6-0870-5d42-8c40bb0aa3d3@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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