From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Oguz Bektas <o.bektas@proxmox.com>
Subject: [pve-devel] applied: Re: [PATCH v2 manager 2/2] lxc: increase limit of max cores from 128 to 8192
Date: Tue, 15 Sep 2020 11:26:54 +0200 [thread overview]
Message-ID: <f63ef4a7-ff29-182a-7d5d-913c1f6efc40@proxmox.com> (raw)
In-Reply-To: <20200915091654.34951-1-o.bektas@proxmox.com>
On 9/15/20 11:16 AM, Oguz Bektas wrote:
> Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
> ---
> www/manager6/lxc/ResourceEdit.js | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
applied, thanks!
Note that you need to use the `--in-reply-to=message-id` CLI switch,
not "--reply-to", they are two different things ;-)
prev parent reply other threads:[~2020-09-15 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 9:16 [pve-devel] " Oguz Bektas
2020-09-15 9:26 ` Thomas Lamprecht [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=f63ef4a7-ff29-182a-7d5d-913c1f6efc40@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=o.bektas@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