From: Arnout Vandecappelle <arnout@mind.be>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: Antoine Tenart <atenart@kernel.org>,
Adam Duskett <aduskett@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] package/refpolicy: Add patches pending the next release
Date: Sat, 8 Jan 2022 14:28:58 +0100 [thread overview]
Message-ID: <44537b02-fabc-6533-bb37-d20268ff508f@mind.be> (raw)
In-Reply-To: <20220107223624.3ba7d348@windsurf>
On 07/01/2022 22:36, Thomas Petazzoni wrote:
> Maxime: do you have that patch 8 broken down into smaller pieces with
> reasonable explanation about each piece?
Just to be clear: "reasonable explanation" means:
- indicate what the problem is;
- why this is different for Buildroot than for others (i.e. why it is a problem
to begin with);
- possible solutions;
- why this specific solution was chosen (which can very well be: the others are
too complicated).
Regards,
Arnout
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-08 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 13:53 [Buildroot] [PATCH 0/3] refpolicy: Allow booting without denied actions Maxime Chevallier
2021-01-07 13:53 ` [Buildroot] [PATCH 1/3] package/refpolicy: Add patches pending the next release Maxime Chevallier
2021-01-07 16:55 ` Thomas Petazzoni
2021-01-08 9:59 ` Maxime Chevallier
2021-05-01 22:10 ` Adam Duskett
2022-01-07 21:36 ` Thomas Petazzoni
2022-01-08 13:28 ` Arnout Vandecappelle [this message]
2021-01-07 13:53 ` [Buildroot] [PATCH 2/3] package/refpolicy: Add a buildroot module Maxime Chevallier
2021-01-07 13:53 ` [Buildroot] [PATCH 3/3] support/testing: improve SELinux test Maxime Chevallier
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=44537b02-fabc-6533-bb37-d20268ff508f@mind.be \
--to=arnout@mind.be \
--cc=aduskett@gmail.com \
--cc=atenart@kernel.org \
--cc=buildroot@buildroot.org \
--cc=maxime.chevallier@bootlin.com \
--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.