Re: [Buildroot] [PATCH v2 1/2] package/raptor: security bump version to 2.0.16

[Peter Korsgaard <peter@korsgaard.com>]

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

 > On 25/06/2023 21:24, Peter Korsgaard wrote:
 >>>>>>> "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.

 >  Oh. I saw you sometimes change the subject line to include "security
 >  bump" when the submitter forgets to...

Sure, if it is a security bump then we normally mention it in the commit
message and I sometimes fix that up when applying if the contributor
forgot to do so - But my point is that I don't just look at

git log --grep 'security bump'

Or something like that, I really skim through all commit on master.

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