From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Noel Ullreich <n.ullreich@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-docs v5] update the PCI(e) docs
Date: Mon, 17 Apr 2023 16:08:58 +0200 [thread overview]
Message-ID: <a645f493-2944-423f-8882-3912b5e3afcd@proxmox.com> (raw)
In-Reply-To: <517256d6-6721-4531-d21d-98c7abddb0a4@proxmox.com>
Am 17/04/2023 um 14:45 schrieb Noel Ullreich:
> Sorry for the borked v4's. Those can be ignored. This is the (hopefully) correctly formatted patch
please reply to the series/patch mail that should be ignored due to $problems,
not the one fixing it. That way, one that has marked the thread with the old
version for review gets the info correctly and can unmark that thread.
As comparison, putting a post it on a light switch stating that another light
switch should not be used as it gives people shocks, is not really _that_ much
of a help to anyone trying to turn on the light and getting to the broken one
first ⚡ ;-)
next prev parent reply other threads:[~2023-04-17 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 12:45 Noel Ullreich
2023-04-17 12:45 ` Noel Ullreich
2023-04-17 14:08 ` Thomas Lamprecht [this message]
2023-06-07 11:34 ` Dominik Csapak
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=a645f493-2944-423f-8882-3912b5e3afcd@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=n.ullreich@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox