From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/php: ignore various CVEs
Date: Sun, 31 Jul 2022 15:02:57 +0300 [thread overview]
Message-ID: <87h72xwkkn.fsf@tarshish> (raw)
In-Reply-To: <pan$9391d$38089e12$245e79a3$aad97a61@ID-313208.user.individual.net>
Hi Bernd,
On Sun, Jul 31 2022, Bernd Kuhls wrote:
> Am Sun, 31 Jul 2022 14:45:27 +0300 schrieb Baruch Siach via buildroot:
>
>> Why do we need to ignore these old CVEs?
>
> to reduce the lenght of the weekly mail:
> https://lists.buildroot.org/pipermail/buildroot/2022-July/646199.html
I share your desire to make the weekly list more useful. My question is
why current version check method does not filter out these CVEs
automatically? I think that the value in moving the list from the
weekly mail to a permanent location in Buildroot source tree is
questionable. An explanation of why this is necessary would be nice.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-31 12:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 11:42 [Buildroot] [PATCH 1/1] package/php: ignore various CVEs Bernd Kuhls
2022-07-31 11:45 ` Baruch Siach via buildroot
[not found] ` <87les9wlk0.fsf__10495.4630181723$1659268091$gmane$org@tarshish>
2022-07-31 11:56 ` Bernd Kuhls
2022-07-31 12:02 ` Baruch Siach via buildroot [this message]
[not found] ` <87h72xwkkn.fsf__20322.4888000236$1659269367$gmane$org@tarshish>
2022-07-31 12:29 ` Bernd Kuhls
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=87h72xwkkn.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=bernd.kuhls@t-online.de \
/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