all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Max Carrara" <m.carrara@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 pve-common 0/4] Section Config: Documentation & Code Cleanup
Date: Thu, 31 Oct 2024 18:10:48 +0100	[thread overview]
Message-ID: <D5A5PJHP6I3G.2FHDPGQYD5LC@proxmox.com> (raw)
In-Reply-To: <20240702141314.445130-1-m.carrara@proxmox.com>

On Tue Jul 2, 2024 at 4:13 PM CEST, Max Carrara wrote:
> Section Config: Documentation & Code Cleanup - v2
> =================================================

Superseded by v3:
https://lore.proxmox.com/pve-devel/20241031170720.338794-1-m.carrara@proxmox.com/

>
> Notable Changes Since v1
> ------------------------
>
>   * Incorporate @Fabian's feedback regarding the docs [0]
>   * Reword commit message of patch 03
>   * NEW: Patch 04: Make sub `delete_from_config` private
>
> Please see the comments in the individual patches for a detailed list of
> changes.
>
> Older Versions
> --------------
>
> v1: https://lists.proxmox.com/pipermail/pve-devel/2024-June/064062.html
>
> References
> ----------
>
> [0]: https://lists.proxmox.com/pipermail/pve-devel/2024-June/064165.html
>
> Summary of Changes
> ------------------
>
> Max Carrara (4):
>   section config: document package and its methods with POD
>   section config: update code style
>   section config: clean up parser logic
>   section config: make subroutine `delete_from_config` private
>
>  src/PVE/SectionConfig.pm | 1200 ++++++++++++++++++++++++++++++++------
>  1 file changed, 1015 insertions(+), 185 deletions(-)



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      parent reply	other threads:[~2024-10-31 17:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02 14:13 Max Carrara
2024-07-02 14:13 ` [pve-devel] [PATCH v2 pve-common 1/4] section config: document package and its methods with POD Max Carrara
2024-07-02 14:13 ` [pve-devel] [PATCH v2 pve-common 2/4] section config: update code style Max Carrara
2024-07-02 14:13 ` [pve-devel] [PATCH v2 pve-common 3/4] section config: clean up parser logic and semantics Max Carrara
2024-07-02 14:13 ` [pve-devel] [PATCH v2 pve-common 4/4] section config: make subroutine `delete_from_config` private Max Carrara
2024-09-16 11:13 ` [pve-devel] [PATCH v2 pve-common 0/4] Section Config: Documentation & Code Cleanup Max Carrara
2024-10-31 17:10 ` Max Carrara [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=D5A5PJHP6I3G.2FHDPGQYD5LC@proxmox.com \
    --to=m.carrara@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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal