all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Oguz Bektas <o.bektas@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] SPAM: [PATCH lxcfs] bump version to 4.0.7-pve1
Date: Thu, 15 Apr 2021 12:47:49 +0200	[thread overview]
Message-ID: <e63d495a-cfb2-3e79-bb2b-a7eae2a0d67a@proxmox.com> (raw)
In-Reply-To: <20210415094430.GA25302@gaia.proxmox.com>

On 15.04.21 11:44, Oguz Bektas wrote:
> hi,
> 
>> please ensure that your git-send-email does not picks up S-b, R-b, etc. git trailers
>> of patches by patches and wrongly CC's those people like happened here.
> oops sorry about that.
> 
>> Further, separate debian/changelog entries from the actual changes, in general
>> rather not send updates to debian/changelog.
>>
>> It would be also good to have a short summary of changes/fixes/features from that
>> new release, i.e., why should be update (what's fixed, or what's changed and thus
>> a potential regression?)...
> it's a minor release and the main highlight is the improvements in swap behavior
> consistency.
> 
> basically the previously cherry-picked patches for some swap
> and memory improvements are now merged upstream.
> 
> https://discuss.linuxcontainers.org/t/lxcfs-4-0-7-lts-has-been-released/9893
> 

So this has basically zero value... I'd like to avoid generating work by just
redoing a release with the exact state we have already build and released in
December 2020...




      reply	other threads:[~2021-04-15 10:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 12:24 Oguz Bektas
2021-04-14 13:57 ` Thomas Lamprecht
2021-04-15  9:44   ` Oguz Bektas
2021-04-15 10:47     ` 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=e63d495a-cfb2-3e79-bb2b-a7eae2a0d67a@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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal