From: Alwin Antreich via pve-devel <pve-devel@lists.proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: Alwin Antreich <alwin@antreich.com>
Subject: Re: [pve-devel] [PATCH docs] pveceph: update OSD memory considerations
Date: Wed, 29 Oct 2025 09:40:23 +0000 [thread overview]
Message-ID: <mailman.369.1761730827.362.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <mailman.200.1758392484.390.pve-devel@lists.proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 4467 bytes --]
From: "Alwin Antreich" <alwin@antreich.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs] pveceph: update OSD memory considerations
Date: Wed, 29 Oct 2025 09:40:23 +0000
Message-ID: <1143add647b317c21eaf43298092e812fce62628@antreich.com>
superseded by: https://lore.proxmox.com/pve-devel/mailman.365.1761730049.362.pve-devel@lists.proxmox.com/T/#u
September 20, 2025 at 8:21 PM, "Alwin Antreich via pve-devel" <pve-devel@lists.proxmox.com mailto:pve-devel@lists.proxmox.com?to=%22Alwin%20Antreich%20via%20pve-devel%22%20%3Cpve-devel%40lists.proxmox.com%3E > wrote:
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com mailto:pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-10-29 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250918164549.3018879-1-alwin@antreich.com>
2025-09-19 12:00 ` Aaron Lauterer
2025-09-20 18:21 ` Alwin Antreich via pve-devel
2025-10-29 9:40 ` Alwin Antreich via pve-devel [this message]
2025-09-18 16:45 Alwin Antreich via pve-devel
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=mailman.369.1761730827.362.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=alwin@antreich.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.