From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/util-linux: add missing SOB to patches
Date: Sat, 14 Mar 2020 15:19:03 +0100 [thread overview]
Message-ID: <20200314151903.40101df8@windsurf> (raw)
In-Reply-To: <20200313010418.16872-1-unixmania@gmail.com>
On Thu, 12 Mar 2020 22:04:18 -0300
unixmania at gmail.com wrote:
> From: Carlos Santos <unixmania@gmail.com>
>
> It is required that all patches in packages have the Signed-off-by of
> the contributor who brought them into Buildroot.
>
> Signed-off-by: Carlos Santos <unixmania@gmail.com>
> ---
> package/util-linux/0003-blkdiscard-use-O_EXCL-add-force.patch | 1 +
> .../0004-libfdisk-add-fdisk_set_disklabel_id_from_string.patch | 1 +
> .../0005-sfdisk-add-disk-id-to-change-disk-UUID-ID.patch | 1 +
> 3 files changed, 3 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-03-14 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 1:04 [Buildroot] [PATCH] package/util-linux: add missing SOB to patches unixmania at gmail.com
2020-03-14 14:19 ` Thomas Petazzoni [this message]
2020-03-21 20:05 ` 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=20200314151903.40101df8@windsurf \
--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