From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Stefan Mayr <stefan@mayr-stefan.de>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH common v3 0/2] Fix #7175: replace timezone handling with systemd timedatectl
Date: Mon, 23 Feb 2026 11:02:14 +0100 [thread overview]
Message-ID: <20260223110214.363a12c8@rosa.proxmox.com> (raw)
In-Reply-To: <20260222110205.582-1-stefan@mayr-stefan.de>
Thanks for the quick iteration on this!
For reference:
These 2 patches replace PATCH 4/4 from:
https://lore.proxmox.com/pve-devel/20260125210151.1151-5-stefan@mayr-stefan.de/
The idea being that patch 1/2 is applied first - then the patches for
pve-container, pve-manager, pmg-api, with a versioned dependency bump on
libpve-common-perl. Once this is rolled PATCH 2/2 from this series can be
applied as well (breaking pve-container, pve-manager, pmg-api not
containing the patches from the v2).
3 tiny nits, which are mostly for any future patches - the complete series
is fine as is IMO.
nit: I'd use different first line for the commit message of each patch
e.g.:
1/2: fix #7175: add timezonectl helpers to PVE::Systemd
2/2: fix #7175: drop deprecated /etc/timezone file helpers
this can be fixed up on applying.
nit: sending the complete series again (even if patches for the
other repositories did not change at all) helps in having all needed
things in one thread - the duplicate mails are less of a problem.
nit: it seems you set my e-mail as reply-to header for this series (this
should not be an issue, as most people hit "Reply All" in their
mail-clients anyway, but could cause some confusion) - maybe you wanted to
add me in CC (`--cc s.ivanov@proxmox.com` for git send-email)?
As the 2 patches together here amount to the same result as the patch for
pve-common in the v2 - my:
Reviewed-by: Stoiko Ivanov <s.ivanov@proxmox.com>
Tested-by: Stoiko Ivanov <s.ivanov@proxmox.com>
still applies (and I quickly checked applying only patch 1/2 on a test-vm
of mine)
Thanks again for your work on this and making the effort to address the
feedback - much appreciated!
stoiko
On Sun, 22 Feb 2026 12:02:03 +0100
Stefan Mayr <stefan@mayr-stefan.de> wrote:
> This splits the patch to pve-common into two parts:
> 1. adds functions for systemd timedatectl
> 2. removes handling deprecated /etc/timezone from INotify module
>
>
>
>
next prev parent reply other threads:[~2026-02-23 10:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 21:01 [pve-devel] [PATCH common, container, manager and pmg-api v2 0/4] " Stefan Mayr
2026-01-25 21:01 ` [pve-devel] [PATCH manager v2 1/4] " Stefan Mayr
2026-01-25 21:01 ` [pve-devel] [PATCH container v2 2/4] " Stefan Mayr
2026-01-25 21:01 ` [pve-devel] [PATCH pmg-api v2 3/4] " Stefan Mayr
2026-01-25 21:01 ` [pve-devel] [PATCH common v2 4/4] " Stefan Mayr
2026-02-18 19:53 ` [pve-devel] [PATCH common, container, manager and pmg-api v2 0/4] " Stefan Mayr
2026-02-19 8:13 ` Fabian Grünbichler
2026-02-20 11:48 ` Stoiko Ivanov
2026-02-22 11:02 ` [PATCH common v3 0/2] " Stefan Mayr
2026-02-23 10:02 ` Stoiko Ivanov [this message]
2026-02-22 11:02 ` [PATCH common v3 1/2] " Stefan Mayr
2026-02-22 11:02 ` [PATCH common v3 2/2] " Stefan Mayr
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=20260223110214.363a12c8@rosa.proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=stefan@mayr-stefan.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.