Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Bernd Kuhls <bernd@kuhls.net>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/2] package/raptor: security bump version to 2.0.16
Date: Sun, 25 Jun 2023 21:24:33 +0200	[thread overview]
Message-ID: <87r0pzny4u.fsf@48ers.dk> (raw)
In-Reply-To: <727a340c-9b87-eb4d-8291-5b97a256d9b1@mind.be> (Arnout Vandecappelle's message of "Sun, 25 Jun 2023 21:18:21 +0200")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

 > On 22/06/2023 07:17, Bernd Kuhls wrote:
 >> This version included the patches removed by this commit, no new CVEs
 >> were fixed.

 >  So, I guess we shouldn't call it a "security bump" then? AFAIU the
 >  only reason to call it security bump is to flag to Peter that it
 > should be backported to stable.


And that is even not necessary. I do look at all commits getting applied
to master to (try to) decide if something should be backported, E.G. if
it is a (security) bugfix and also applies to the version in LTS.

If you already had a look at think it should be backported, then just
state that in the commit message (E.G. fixes foo since the bump to
version x.y.z in commit sha1).

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-06-25 19:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-22  5:17 [Buildroot] [PATCH v2 1/2] package/raptor: security bump version to 2.0.16 Bernd Kuhls
2023-06-22  5:17 ` [Buildroot] [PATCH v2 2/2] package/raptor: fix build with newer versions of libxml2 Bernd Kuhls
2023-06-25 19:19   ` Arnout Vandecappelle via buildroot
2023-06-25 19:18 ` [Buildroot] [PATCH v2 1/2] package/raptor: security bump version to 2.0.16 Arnout Vandecappelle via buildroot
2023-06-25 19:24   ` Peter Korsgaard [this message]
2023-06-25 19:34     ` Arnout Vandecappelle via buildroot
2023-06-25 19:42       ` Peter Korsgaard
2023-06-25 19:44 ` Arnout Vandecappelle via buildroot

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=87r0pzny4u.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=arnout@mind.be \
    --cc=bernd@kuhls.net \
    --cc=buildroot@buildroot.org \
    /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