public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Alexandre Derumier <aderumier@odiso.com>
Subject: [pve-devel] applied:  [PATCH ifupdown2 0/6] bump to 3.2.0
Date: Sat, 20 May 2023 16:22:24 +0200	[thread overview]
Message-ID: <966f438f-b96d-9057-8cb8-41138c704ad6@proxmox.com> (raw)
In-Reply-To: <20230515224710.1331004-1-aderumier@odiso.com>

Am 16/05/2023 um 00:47 schrieb Alexandre Derumier:
> This patch series bump version to 3.2.0.
> 
> This need update of proxmox ifupdown2 mirror to last master
> a0522546b848435115a20eb647f87ade01761a33 commit , as
> the 3.2.0 tagged version is missing 1 patch fix.

FYI: After checking out the submodule at that commit, it can add
be added as normal commit change in the outer repository, that way
you can already send it along to ensure that the one applying
it doesn't forgets to do that (or chooses a wrong commit by mistake).

> 
> I have remove old upstreamed patches,
> and add a new patch for ipv6 slaac support.
> 
> I only have tested with debian11 currently.
> 
> 
> Alexandre Derumier (6):
>   patch: patch5: fix code nit
>   patch: remove old upstreamed patches
>   patch: reorder patches
>   patch: add ipv6 slaac support upstream patch
>   patch: remove lacp bond min-links=0 warning
>   bump version to 3.2.0-1+pmx1
applied, thanks!

FYI: I reworked the build system a bit, i.e., merged upstreams debian/ into ours
and dropped our patches related to that. This means that we have check if there
are any packaging specific changes on new releases, but also allows us to build
source pacakages for clean building and to make changes w.r.t. packaging much
easier. So if anything has to change in the debian/ folder in the future you can
just edit that directly in the top-level one, no need for patches there any more.




      parent reply	other threads:[~2023-05-20 14:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 22:47 [pve-devel] " Alexandre Derumier
2023-05-15 22:47 ` [pve-devel] [PATCH ifupdown2 1/6] patch: patch5: fix code nit Alexandre Derumier
2023-05-15 22:47 ` [pve-devel] [PATCH ifupdown2 2/6] patch: remove old upstreamed patches Alexandre Derumier
2023-05-15 22:47 ` [pve-devel] [PATCH ifupdown2 3/6] patch: reorder patches Alexandre Derumier
2023-05-15 22:47 ` [pve-devel] [PATCH ifupdown2 4/6] patch: add ipv6 slaac support upstream patch Alexandre Derumier
2023-05-15 22:47 ` [pve-devel] [PATCH ifupdown2 5/6] patch: remove lacp bond min-links=0 warning Alexandre Derumier
2023-05-15 22:47 ` [pve-devel] [PATCH ifupdown2 6/6] bump version to 3.2.0-1+pmx1 Alexandre Derumier
2023-05-20 14:22 ` 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=966f438f-b96d-9057-8cb8-41138c704ad6@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=aderumier@odiso.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal