all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Max Carrara" <m.carrara@proxmox.com>
To: "Thomas Lamprecht" <t.lamprecht@proxmox.com>,
	"Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] partially-applied-series: [PATCH v3 pve-common 0/5] Section Config: Documentation & Code Cleanup
Date: Thu, 14 Nov 2024 09:37:33 +0100	[thread overview]
Message-ID: <D5LRK6THXWOP.8WVJ7X4QCIHO@proxmox.com> (raw)
In-Reply-To: <dd4eb46a-5911-45ba-a3dc-a13859d8c96d@proxmox.com>

On Mon Nov 11, 2024 at 2:59 PM CET, Thomas Lamprecht wrote:
> Am 31.10.24 um 18:07 schrieb Max Carrara:
> > Section Config: Documentation & Code Cleanup - v3
> > =================================================
> > 
> > Notable Changes Since v2
> > ------------------------
> > 
> >   * Adapt documentation syntax and style
> >   * Use less emphasis codes `I<>`
> >   * Add commit to fix spelling
> > 
> > Please see the comments in the individual patches for a detailed list of
> > changes.
> > 
> > Older Versions
> > --------------
> > 
> > v2: https://lore.proxmox.com/pve-devel/20240702141314.445130-1-m.carrara@proxmox.com/
> > v1: https://lore.proxmox.com/pve-devel/20240604092850.126083-1-m.carrara@proxmox.com/
> > 
> > Summary of Changes
> > ------------------
> > 
> > Max Carrara (5):
> >   section config: document package and its methods with POD
> >   section config: update code style
> >   section config: clean up parser logic and semantics
>
> ^- skipped this one for now.
>
> >   section config: make subroutine `delete_from_config` private
> >   section config: fix spelling of variable
> > 
> >  src/PVE/SectionConfig.pm | 1197 ++++++++++++++++++++++++++++++++------
> >  1 file changed, 1008 insertions(+), 189 deletions(-)
> > 
>
> After talking with Stefan Hanreich off-list he mentioned that this series was
> helpfull to some recent section-config related work of his, so partially applied
> this series, thanks!

Thanks a bunch!

Regarding the commit that was left out: I'll see if I can send this in
as part of a separate series that perhaps also clears some other stuff
up and adds some tests, since I'm in refactor-land at the moment anyway.



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


      reply	other threads:[~2024-11-14  8:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31 17:07 [pve-devel] " Max Carrara
2024-10-31 17:07 ` [pve-devel] [PATCH v3 pve-common 1/5] section config: document package and its methods with POD Max Carrara
2024-10-31 17:07 ` [pve-devel] [PATCH v3 pve-common 2/5] section config: update code style Max Carrara
2024-10-31 17:07 ` [pve-devel] [PATCH v3 pve-common 3/5] section config: clean up parser logic and semantics Max Carrara
2024-11-11 15:29   ` Thomas Lamprecht
2024-10-31 17:07 ` [pve-devel] [PATCH v3 pve-common 4/5] section config: make subroutine `delete_from_config` private Max Carrara
2024-10-31 17:07 ` [pve-devel] [PATCH v3 pve-common 5/5] section config: fix spelling of variable Max Carrara
2024-11-11 13:59 ` [pve-devel] partially-applied-series: [PATCH v3 pve-common 0/5] Section Config: Documentation & Code Cleanup Thomas Lamprecht
2024-11-14  8:37   ` 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=D5LRK6THXWOP.8WVJ7X4QCIHO@proxmox.com \
    --to=m.carrara@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@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