public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH docs v2 0/3] network: update & reword
Date: Mon, 27 Jun 2022 15:15:55 +0200	[thread overview]
Message-ID: <09736d03-2bea-e1c6-cf39-ab960d4d26ff@proxmox.com> (raw)
In-Reply-To: <20220602092251.1393709-1-a.lauterer@proxmox.com>

ping?

On 6/2/22 11:22, Aaron Lauterer wrote:
> 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(-)
> 




  parent reply	other threads:[~2022-06-27 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  9:22 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 ` Aaron Lauterer [this message]
2022-09-12 16:02 ` [pve-devel] applied-series: [PATCH docs v2 0/3] network: update & reword 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=09736d03-2bea-e1c6-cf39-ab960d4d26ff@proxmox.com \
    --to=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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal