From: Sebastian Luksch via pve-devel <pve-devel@lists.proxmox.com>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Cc: Sebastian Luksch <bugzilla.proxmox.com@lookshe.org>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager/pmg-api 0/2] Fix #6748: correct usage of Term::ReadLine
Date: Thu, 04 Sep 2025 19:52:59 +0200 [thread overview]
Message-ID: <mailman.285.1757067470.418.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <1756986959.a64mhit0hv.astroid@yuna.none>
[-- Attachment #1: Type: message/rfc822, Size: 5248 bytes --]
From: Sebastian Luksch <bugzilla.proxmox.com@lookshe.org>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager/pmg-api 0/2] Fix #6748: correct usage of Term::ReadLine
Date: Thu, 04 Sep 2025 19:52:59 +0200
Message-ID: <e855fbb33d3dc1bcc9658ecb7912a29e@lookshe.org>
Hi,
thanks for your work maintaining the project. I noticed the request to
fill out a CLA, and I wanted to share a quick thought.
While I appreciate the importance of formal contribution processes, I
find the CLA requirements a bit too involved for such small patches,
especially considering the amount of personal information requested. I'd
prefer not to go through that process for this minor contribution.
If there's a way to accept small patches under the existing project
license (AGPL) without requiring a CLA, I'd be happy contributing in
that manner. Otherwise, I understand if you can't include the patches.
Thanks again for your time and consideration.
Best regards,
Sebastian
Am 2025-09-04 13:56, schrieb Fabian Grünbichler:
> On September 2, 2025 8:20 pm, Sebastian Luksch via pve-devel wrote:
>> The update to debian trixie also updated libterm-readline-gnu-perl to
>> version
>> 1.46-1. Since this version it is not possible to create more than one
>> Term:ReadLine object. These patches fix the last occurences where
>> multiple
>> objects were created in all active repositories found under
>> https://git.proxmox.com.
>
> Hi!
>
> thanks for your patches. could you please also send a signed CLA as
> described in our Developer Documentation[0] to office@proxmox.com?
>
> thanks!
> Fabian
>
> 0:
> https://pve.proxmox.com/wiki/Developer_Documentation#Software_License_and_Copyright
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-09-05 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 18:20 Sebastian Luksch via pve-devel
2025-09-04 11:56 ` Fabian Grünbichler
2025-09-04 17:52 ` Sebastian Luksch via pve-devel [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=mailman.285.1757067470.418.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=bugzilla.proxmox.com@lookshe.org \
--cc=f.gruenbichler@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