From: Max Carrara <m.carrara@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 quincy-stable-8 ceph 0/2] Backport Patches for Reef for Quincy
Date: Fri, 26 Jan 2024 16:44:38 +0100 [thread overview]
Message-ID: <20240126154440.657816-1-m.carrara@proxmox.com> (raw)
Updated series that includes an unstaged change I had missed to amend
regarding the corrected typo mentioned in the recent patch for master [0].
Woops!
[0]: https://lists.proxmox.com/pipermail/pve-devel/2024-January/061499.html
Max Carrara (2):
patches: include patches regarding RocksDB and dashboard from master
patch: fix `ceph dashboard` subcommand becoming unavailable on crash
...hboard-simplify-authentication-proto.patch | 279 ++++++++++++++++++
patches/0021-debian-rules-fix-buildtype.patch | 22 --
...move-ability-to-create-and-check-TLS.patch | 128 ++++++++
...cksb-inherit-parent-cmake-cxx-flags.patch} | 0
patches/series | 5 +-
5 files changed, 410 insertions(+), 24 deletions(-)
create mode 100644 patches/0021-backport-mgr-dashboard-simplify-authentication-proto.patch
delete mode 100644 patches/0021-debian-rules-fix-buildtype.patch
create mode 100644 patches/0022-mgr-dashboard-remove-ability-to-create-and-check-TLS.patch
rename patches/{0022-rocksb-inherit-parent-cmake-cxx-flags.patch => 0023-rocksb-inherit-parent-cmake-cxx-flags.patch} (100%)
--
2.39.2
next reply other threads:[~2024-01-26 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 15:44 Max Carrara [this message]
2024-01-26 15:44 ` [pve-devel] [PATCH v2 quincy-stable-8 ceph 1/2] patches: include patches regarding RocksDB and dashboard from master Max Carrara
2024-02-02 18:13 ` Thomas Lamprecht
2024-02-15 13:09 ` Thomas Lamprecht
2024-02-15 17:03 ` Max Carrara
2024-01-26 15:44 ` [pve-devel] [PATCH v2 quincy-stable-8 ceph 2/2] patch: fix `ceph dashboard` subcommand becoming unavailable on crash Max Carrara
2024-02-02 18:11 ` [pve-devel] applied-series: [PATCH v2 quincy-stable-8 ceph 0/2] Backport Patches for Reef for Quincy Thomas Lamprecht
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=20240126154440.657816-1-m.carrara@proxmox.com \
--to=m.carrara@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 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.