All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Frank Vanbever via buildroot <buildroot@buildroot.org>
Cc: Frank Vanbever <frank.vanbever@mind.be>
Subject: Re: [Buildroot] [PATCH 1/1] package/libmodsecurity: security bump to version 3.0.10
Date: Thu, 24 Aug 2023 20:56:56 +0200	[thread overview]
Message-ID: <20230824205656.23594903@windsurf> (raw)
In-Reply-To: <20230823145300.1499071-1-frank.vanbever@mind.be>

Hello Frank,

On Wed, 23 Aug 2023 16:53:00 +0200
Frank Vanbever via buildroot <buildroot@buildroot.org> wrote:

> - Fixes CVE-2023-38285 [1]
> - Adapted 0001-configure.ac-drop-usage-of-git-at-configure-time.patch due to
>   upstream moving to autoconf portable shell constructs.
> - Added missing Upstream comments

I've applied to master, but after dropping this part. Indeed, I think
adding "Upstream: N/A" to "resolve" the checkpackage warning is really
not useful. What's useful is to submit the patches upstream :-)

Thanks!

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

  reply	other threads:[~2023-08-24 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 14:53 [Buildroot] [PATCH 1/1] package/libmodsecurity: security bump to version 3.0.10 Frank Vanbever via buildroot
2023-08-24 18:56 ` Thomas Petazzoni via buildroot [this message]
2023-09-13 15:57 ` Peter Korsgaard

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=20230824205656.23594903@windsurf \
    --to=buildroot@buildroot.org \
    --cc=frank.vanbever@mind.be \
    --cc=thomas.petazzoni@bootlin.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.