From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Hrdlicka <s.hrdlicka@proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager] ceph install wizard: fix #3597: don't autofill network
Date: Wed, 8 Jun 2022 09:04:22 +0200 [thread overview]
Message-ID: <19cdf53e-3435-1818-b807-e95704f09338@proxmox.com> (raw)
In-Reply-To: <bd4797ff-730b-ef28-1294-a7fc2273d3ee@proxmox.com>
Am 02/06/2022 um 15:30 schrieb Stefan Hrdlicka:
> Tried it and works as expected.
>
> I can't answer the original mail, since I joined the mailing list a bit later :).
Really no biggie, but FYI, it depends on the capabillities of your mail client/MUA but
normally you'd only need to add a "In-Reply-To: <message-id>" header, can often be done
by simply clicking the mail address link at the top of the mailman archives, which includes
that part in it's mailto: href, e.g. for this one it would have been [0].
I use that sometimes for lists I'm not subscribed too, e.g., as they're high volume or
niche.
[0]: https://lists.proxmox.com/pipermail/pve-devel/2022-May/052890.html
Other small nit: please avoid top posting [1], most MUA's can be configured where to place
the cursor plus some empty space by default on reply.
[1]: https://git-send-email.io/top-posting.html
> Tested-by: Stefan Hrdlicka<s.hrdlicka@proxmox.com>
applied with that, I also changed the commit message's subject to better match our style
("fix #bug" in the front, then a bit more specific about what was touched) thanks!
prev parent reply other threads:[~2022-06-08 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 14:05 [pve-devel] " Aaron Lauterer
2022-06-01 10:27 ` Aaron Lauterer
2022-06-02 13:30 ` Stefan Hrdlicka
2022-06-08 7:04 ` 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=19cdf53e-3435-1818-b807-e95704f09338@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hrdlicka@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