all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com,
	"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: applied: [PATCH proxmox-backup 0/4] move group/namespace logging improvements
Date: Tue, 28 Apr 2026 16:24:14 +0200	[thread overview]
Message-ID: <177738625275.1185355.13511712527918759120.b4-ty@b4> (raw)
In-Reply-To: <20260427120234.634681-1-f.gruenbichler@proxmox.com>

On Mon, 27 Apr 2026 14:02:24 +0200, Fabian Grünbichler wrote:
> just cosmetic improvements
> 
> Fabian Grünbichler (4):
>   move group: use human-readable snapshot timestamp in check
>   move group: split overly long error message
>   move namespace: move context log line before check
>   move namespace: use group(s)/namespace(s) consistently
> 
> [...]

Applied, thanks!

I dropped the stray has_manifest() addition from the first one and split out
s/overlap/mismatch from the "move namespace: move context log line before
check" one into its own commit, as that was unrelated and as the doc-comment of
the check_merge_invariants it was worth it compared to the tiny cost.

[1/4] move group: use human-readable snapshot timestamp in check
      commit: a6f5567f08e6dbd2e8891375bfcab3a5232cb4f0
[2/4] move group: split overly long error message
      commit: 4de09c1b73b6f379bbe59b52643eea1368c54856
[3/4] move namespace: move context log line before check
      commit: a6261476459805bb49a9a7bd71caa470b1986087
[4/4] move namespace: use group(s)/namespace(s) consistently
      commit: 3206d221ef3de82b0d0d83b9e075f09507b064f0




      parent reply	other threads:[~2026-04-28 14:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 12:02 [PATCH proxmox-backup 0/4] move group/namespace logging improvements Fabian Grünbichler
2026-04-27 12:02 ` [PATCH proxmox-backup 1/4] move group: use human-readable snapshot timestamp in check Fabian Grünbichler
2026-04-27 12:02 ` [PATCH proxmox-backup 2/4] move group: split overly long error message Fabian Grünbichler
2026-04-27 12:02 ` [PATCH proxmox-backup 3/4] move namespace: move context log line before check Fabian Grünbichler
2026-04-27 12:02 ` [PATCH proxmox-backup 4/4] move namespace: use group(s)/namespace(s) consistently Fabian Grünbichler
2026-04-28 14:24 ` 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=177738625275.1185355.13511712527918759120.b4-ty@b4 \
    --to=t.lamprecht@proxmox.com \
    --cc=f.gruenbichler@proxmox.com \
    --cc=pbs-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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal