From: zdykstra <zdykstra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [NOMERGE] zfs: update to 2.2.0.
Date: Wed, 02 Aug 2023 17:15:29 +0200 [thread overview]
Message-ID: <20230802151529.cJHyPJvTYNlFFEyTnjFi591WDn1AU5Devbu8PShElX4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45365@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 302 bytes --]
New comment by zdykstra on void-packages repository
https://github.com/void-linux/void-packages/pull/45365#issuecomment-1662398857
Comment:
Determining which course of action to follow is in @Vaelatern's court. Barring any additional input from him, I won't take any action to resolve this, for now.
next prev parent reply other threads:[~2023-08-02 15:15 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 21:34 [PR PATCH] DRAFT: " zdykstra
2023-08-01 1:50 ` [PR PATCH] [Updated] [NOMERGE] " zdykstra
2023-08-01 2:42 ` zdykstra
2023-08-01 10:59 ` dkwo
2023-08-02 11:21 ` r-ricci
2023-08-02 13:50 ` zdykstra
2023-08-02 15:11 ` r-ricci
2023-08-02 15:15 ` zdykstra [this message]
2023-08-02 16:55 ` Vaelatern
2023-08-03 19:49 ` Vaelatern
2023-08-03 23:13 ` r-ricci
2023-08-04 15:10 ` r-ricci
2023-08-11 16:43 ` Vaelatern
2023-08-11 19:42 ` [PR PATCH] [Updated] " zdykstra
2023-08-11 19:42 ` zdykstra
2023-08-11 19:53 ` zdykstra
2023-08-11 19:54 ` [PR PATCH] [Updated] " zdykstra
2023-08-11 19:54 ` zdykstra
2023-08-11 19:56 ` classabbyamp
2023-08-11 20:01 ` [PR PATCH] [Updated] " zdykstra
2023-08-11 20:23 ` zdykstra
2023-08-16 20:15 ` [PR REVIEW] " r-ricci
2023-08-17 2:40 ` Vaelatern
2023-08-17 2:41 ` Vaelatern
2023-08-17 2:42 ` [PR PATCH] [Updated] " zdykstra
2023-08-22 14:41 ` zdykstra
2023-08-22 16:33 ` Vaelatern
2023-08-22 16:40 ` zdykstra
2023-08-22 17:23 ` classabbyamp
2023-08-22 18:26 ` Vaelatern
2023-08-22 18:29 ` zdykstra
2023-08-23 19:28 ` [PR PATCH] [Updated] " zdykstra
2023-08-24 0:50 ` [PR PATCH] [Updated] [NOMERGE] zfs: update to 2.2.0, add zfs-lts package zdykstra
2023-08-24 2:18 ` ahesford
2023-08-24 2:40 ` [PR PATCH] [Updated] " zdykstra
2023-09-04 17:54 ` zdykstra
2023-09-08 1:18 ` zdykstra
2023-09-08 1:43 ` zdykstra
2023-09-08 15:15 ` zdykstra
2023-09-08 16:33 ` Vaelatern
2023-09-09 2:13 ` [PR PATCH] [Updated] " zdykstra
2023-09-09 2:26 ` zdykstra
2023-09-09 3:55 ` zdykstra
2023-09-09 4:02 ` zdykstra
2023-09-09 4:11 ` zdykstra
2023-09-09 4:13 ` zdykstra
2023-09-09 4:24 ` zdykstra
2023-09-09 4:30 ` zdykstra
2023-09-09 4:37 ` zdykstra
2023-09-13 15:40 ` [PR PATCH] [Updated] " zdykstra
2023-09-30 20:22 ` darkbasic
2023-09-30 20:56 ` darkbasic
2023-10-02 22:53 ` [PR PATCH] [Updated] " zdykstra
2023-10-07 23:15 ` zdykstra
2023-10-13 17:25 ` zdykstra
2023-10-13 19:38 ` [PR PATCH] [Updated] " zdykstra
2023-10-13 21:48 ` Vaelatern
2023-10-13 21:49 ` Vaelatern
2023-10-13 21:54 ` ahesford
2023-10-13 22:11 ` classabbyamp
2023-10-14 7:47 ` darkbasic
2023-10-14 15:28 ` heppu
2023-10-17 20:05 ` Vaelatern
2023-10-17 23:58 ` [PR REVIEW] " classabbyamp
2023-10-18 0:13 ` [PR PATCH] [Updated] " zdykstra
2023-10-18 0:14 ` [PR REVIEW] " zdykstra
2023-10-18 1:59 ` [PR PATCH] [Merged]: " classabbyamp
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=20230802151529.cJHyPJvTYNlFFEyTnjFi591WDn1AU5Devbu8PShElX4@z \
--to=zdykstra@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).