From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "José Pekkarinen" <jose.pekkarinen@unikie.com>
Cc: "buildroot@uclibc.org" <buildroot@uclibc.org>
Subject: Re: [Buildroot] [PATCH] Remove deprecated matchpathcon calls
Date: Tue, 27 Jul 2021 14:43:40 +0200 [thread overview]
Message-ID: <20210727144340.7fecf359@windsurf> (raw)
In-Reply-To: <CAJPV9MpuxCHXRAf2zTeuZnHB1FjiwtJHA6-UxEvHFFJ8WWg4gw@mail.gmail.com>
Hello José,
On Tue, 27 Jul 2021 15:21:21 +0300
José Pekkarinen <jose.pekkarinen@unikie.com> wrote:
> Thanks for quickly addressing this Thomas. If I may, as this is a
> fix, is there any process to backport it to the stable versions? Perhaps
> I have to resend it to the mailing list with another label? My customer
> would be glad to take it from there.
Our process to backport to stable versions is that Peter Korsgaard (one
of the Buildroot co-maintainers) reviews the entire set of commits that
go into master, and whenever a commit is a security bump or a fix, it
gets backported to 2021.02.x.
I have Cc'ed Peter on your request to make sure it is clear to him that
commit 90dd1d6178b01f6da3e59e43d0c7efdf984a72d8 is a fix that should be
backported to 2021.02.x.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-07-27 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 9:51 [Buildroot] [PATCH] Remove deprecated matchpathcon calls José Pekkarinen
2021-07-24 21:38 ` Thomas Petazzoni
[not found] ` <CAJPV9MpuxCHXRAf2zTeuZnHB1FjiwtJHA6-UxEvHFFJ8WWg4gw@mail.gmail.com>
2021-07-27 12:43 ` Thomas Petazzoni [this message]
2021-07-27 12:46 ` José Pekkarinen
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=20210727144340.7fecf359@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@uclibc.org \
--cc=jose.pekkarinen@unikie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox