From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] sunxi-mali-mainline: add EULA license file
Date: Sat, 25 Aug 2018 09:51:31 +0200 [thread overview]
Message-ID: <20180825095131.14ca9459@windsurf> (raw)
In-Reply-To: <f4eab7a8-6eff-889e-ff8f-636c83cfbe8a@micronovasrl.com>
Hello Giulio,
On Sat, 25 Aug 2018 02:22:50 +0200, Giulio Benetti wrote:
> Even if it could be acceptable(maybe?), I would like to make the best.
> Did I have also in this case split into 2 different commits?
> One for package and one for hash file?
> Because thinking about bisection,
> even if I apply them one by one, it builds ok,
> except for warning if there is not hash file.
> So maybe I should do 2 patches in these order:
> - sunxi-mali-mainline: add EULA license file
> - sunxi-mali-mainline: add hash file
Do it the other way around:
- Add the hash file, without the hash for the EULA file, just for the
tarball.
- Add the license file information + the hash of the license file.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-25 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 23:47 [Buildroot] [PATCH] sunxi-mali-mainline: add EULA license file Giulio Benetti
2018-08-25 0:22 ` Giulio Benetti
2018-08-25 7:51 ` Thomas Petazzoni [this message]
2018-08-25 11:18 ` Giulio Benetti
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=20180825095131.14ca9459@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