> Yes, exactly! Make sure to also add a version in the commit message(e.g:
> "[pve-devel] [PATCH v2 pve-manager 4/5] fix #3593"), and describe which
> changes were made since the last version. You can take a look at other
> mails so see how it is done:
> https://lists.proxmox.com/pipermail/pve-deve
On 08.06.2022 15:21, Daniel Bowder wrote:
Thank you for your patches!
You are welcome.
Regarding the formatting: Please make sure to follow our Perl and
Javascript style guides [0][1] and the Developer Documentation [2]. All
your patches use a nonconformant indentation :/
I do apologize for t
> Thank you for your patches!
You are welcome.
> Regarding the formatting: Please make sure to follow our Perl and
> Javascript style guides [0][1] and the Developer Documentation [2]. All
> your patches use a nonconformant indentation :/
I do apologize for that. I read [0] and [2] in their entire
On 08.06.2022 13:54, Daniel Bowder wrote:
These five patches add the ability to pin a QEMU VMs processes to a defined set of CPU
cores. The changes required spanned multiple repos and have all been included in these
five patches. The patches add "cpuset" as an option in the qm configuration
fi
These five patches add the ability to pin a QEMU VMs processes to a defined set
of CPU cores. The changes required spanned multiple repos and have all been
included in these five patches. The patches add "cpuset" as an option in the qm
configuration file and enable the editing of this parameter
