From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH docs v2 0/3] network: update & reword
Date: Mon, 12 Sep 2022 18:02:35 +0200 [thread overview]
Message-ID: <5af9a491-5897-7066-2f2c-ec4c378f6b39@proxmox.com> (raw)
In-Reply-To: <20220602092251.1393709-1-a.lauterer@proxmox.com>
Am 02/06/2022 um 11:22 schrieb Aaron Lauterer:
> Update the network section to
> - remove mentioning ifup & ifdown as it can break connections of running
> guests
> - ifupdown2 is default now, we can remove the verbose install guide
> - rework the introduction to make a few conecpts clear to people that
> are not used to it yet
>
> changes since v1:
> * add note about ifupdown2 on a PVE on top of Debian installation
>
> Aaron Lauterer (3):
> network: remove ifup ifdown as it won't reattach guests
> network: adapt apply config section to PVE 7
> network: rework introduction for people with less experience
>
> pve-network.adoc | 62 +++++++++++++++++++++++++-----------------------
> 1 file changed, 32 insertions(+), 30 deletions(-)
>
applied, with a followup (see git log for details), thanks!
prev parent reply other threads:[~2022-09-12 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 9:22 [pve-devel] " Aaron Lauterer
2022-06-02 9:22 ` [pve-devel] [PATCH docs v2 1/3] network: remove ifup ifdown as it won't reattach guests Aaron Lauterer
2022-09-12 16:02 ` [pve-devel] applied: " Thomas Lamprecht
2022-06-02 9:22 ` [pve-devel] [PATCH docs v2 2/3] network: adapt apply config section to PVE 7 Aaron Lauterer
2022-06-02 9:22 ` [pve-devel] [PATCH docs v2 3/3] network: rework introduction for people with less experience Aaron Lauterer
2022-06-27 13:15 ` [pve-devel] [PATCH docs v2 0/3] network: update & reword Aaron Lauterer
2022-09-12 16:02 ` 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=5af9a491-5897-7066-2f2c-ec4c378f6b39@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.lauterer@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