All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: Peter Seiderer <ps.report@gmx.net>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH/next 1/2] package/postgresql: security bump version to 13.5
Date: Sat, 13 Nov 2021 18:08:46 +0100	[thread overview]
Message-ID: <20211113180846.2009b6e4@windsurf> (raw)
In-Reply-To: <20211113170403.2795532-1-bernd.kuhls@t-online.de>

On Sat, 13 Nov 2021 18:04:02 +0100
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:

> Release notes:
> https://www.postgresql.org/about/news/postgresql-141-135-129-1114-1019-and-9624-released-2349/
> 
> Fixes CVE-2021-23214 and CVE-2021-23222.
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> Added this patch for master branch to next branch for easier merging.

Sorry, but I don't understand what you mean here. You're using the past
tense "Added", which I don't really understand. This commit is a
security bump, so why would it go to "next" as specified in your patch
title?

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2021-11-13 17:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-13 17:04 [Buildroot] [PATCH/next 1/2] package/postgresql: security bump version to 13.5 Bernd Kuhls
2021-11-13 17:04 ` [Buildroot] [PATCH/next 2/2] package/postgresql: bump version to 14.1 Bernd Kuhls
2021-11-13 17:08 ` Thomas Petazzoni [this message]
     [not found] ` <20211113180846.2009b6e4__48491.8654475891$1636823353$gmane$org@windsurf>
2021-11-13 18:50   ` [Buildroot] [PATCH/next 1/2] package/postgresql: security bump version to 13.5 Bernd Kuhls
2021-11-14 13:54     ` Thomas Petazzoni

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=20211113180846.2009b6e4@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=bernd.kuhls@t-online.de \
    --cc=buildroot@buildroot.org \
    --cc=ps.report@gmx.net \
    /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.