From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
"t.lamprecht@proxmox.com" <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] is the next pve version 8.0 with debian 12 ? (any planning on patches merge ?)
Date: Fri, 28 Apr 2023 12:15:37 +0000 [thread overview]
Message-ID: <708d7b153fac05bbc23b57f2c5e0114d9e6e62c8.camel@groupe-cyllene.com> (raw)
In-Reply-To: <2fd9041f-d7e4-bffd-f194-c783570e7430@proxmox.com>
Le vendredi 28 avril 2023 à 11:33 +0200, Thomas Lamprecht a écrit :
> And we probably won't accept bigger breaking change after the beta
> is made public. So, continuing the strong guess of mine, I'd say
> if you get anything bigger submitted before ~ mid-may, we got still
> some time for patches rework until ~ end of may.
Ok thanks!
I don't have nothing big in my pipe.
(I only have a patch series for ifupdown2 for ipv6 slaac support, I'm
waiting for ifupdown2 dev review before submiting it to pve-devel)
https://github.com/CumulusNetworks/ifupdown2/pull/259
I'm going on holiday tomorrow for 2 weeks, so Mid-may --> end may,
no problem, I should have time to rebase/rework my previous patches if
needed. (or help to implement network permissions)
for proxmox8, I'll also look to bump frr && ifupdown2 to last versions.
Alexandre
prev parent reply other threads:[~2023-04-28 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 7:15 DERUMIER, Alexandre
2023-04-28 9:33 ` Thomas Lamprecht
2023-04-28 10:09 ` Fabian Grünbichler
2023-04-28 12:04 ` DERUMIER, Alexandre
2023-04-28 12:15 ` DERUMIER, Alexandre [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=708d7b153fac05bbc23b57f2c5e0114d9e6e62c8.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.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.