From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/refpolicy: Add patches pending the next release
Date: Thu, 7 Jan 2021 17:55:43 +0100 [thread overview]
Message-ID: <20210107175543.2fb51ec6@windsurf.home> (raw)
In-Reply-To: <20210107135307.1762186-2-maxime.chevallier@bootlin.com>
Hello,
On Thu, 7 Jan 2021 14:53:05 +0100
Maxime Chevallier <maxime.chevallier@bootlin.com> wrote:
> diff --git a/package/refpolicy/0001-pending-next-release.patch b/package/refpolicy/0001-pending-next-release.patch
> new file mode 100644
> index 0000000000..e049845638
> --- /dev/null
> +++ b/package/refpolicy/0001-pending-next-release.patch
> @@ -0,0 +1,673 @@
> +From 2566e2dac2c759392e0b9f3d442b8489b726cb10 Mon Sep 17 00:00:00 2001
> +From: Antoine Tenart <antoine.tenart@bootlin.com>
> +Date: Mon, 31 Aug 2020 15:38:13 +0200
> +Subject: [PATCH 1/8] [pending next release]
Could you generate patches for packages with git format-patch -N to
avoid the numbering PATCH X/Y ? This is normally caught by "make
check-package".
Also, this particular patch is apparently a huge aggregation of several
individual upstream commits. We do want to have each individual commit
as a separate patch in Buildroot, with a reference to the upstream
commit, a bit like this:
Signed-off-by: Antoine T?nart ...
Upstream: link to upstream commit, or at least commit hash
Signed-off-by: You
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-01-07 16:55 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 [this message]
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
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=20210107175543.2fb51ec6@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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