From: Richard Braun <rbraun@sceen.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] intel-microcode: new package
Date: Fri, 28 Sep 2012 14:17:58 +0200 [thread overview]
Message-ID: <20120928121758.GA2362@mail.sceen.net> (raw)
In-Reply-To: <20120922094203.GA11192@mail.sceen.net>
On Sat, Sep 22, 2012 at 11:42:03AM +0200, Richard Braun wrote:
> Unfortunately no, the microcode file is the only one.
While it's the only file, the license is actually embedded inside, in
plain text. I've modified the package to extract the license as a
separate file in the build directory. The package infrastructure also
had to be slightly change to save legal info for proprietary packages.
Patches will follow.
--
Richard Braun
next prev parent reply other threads:[~2012-09-28 12:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 15:12 [Buildroot] [PATCH] intel-microcode: new package Richard Braun
2012-09-20 20:36 ` Thomas Petazzoni
2012-09-20 21:12 ` Richard Braun
2012-09-21 8:35 ` Thomas Petazzoni
2012-09-22 9:42 ` Richard Braun
2012-09-28 12:17 ` Richard Braun [this message]
2012-09-28 12:20 ` [Buildroot] [PATCH] pkg-infra: produce legal info for proprietary packages Richard Braun
2012-09-28 12:23 ` Thomas Petazzoni
2012-09-28 16:40 ` Thomas De Schampheleire
2012-09-28 17:05 ` Thomas Petazzoni
2012-09-28 18:52 ` Thomas De Schampheleire
2012-09-30 14:22 ` Arnout Vandecappelle
2012-10-02 13:41 ` Luca Ceresoli
2012-10-02 14:35 ` Arnout Vandecappelle
2012-10-02 17:50 ` Thomas De Schampheleire
2012-10-16 15:42 ` Richard Braun
2012-10-20 20:51 ` Luca Ceresoli
2012-10-20 21:55 ` Richard Braun
2012-09-28 12:20 ` [Buildroot] [PATCH] intel-microcode: new package Richard Braun
2012-09-28 12:24 ` Thomas Petazzoni
2012-09-29 9:31 ` Thomas De Schampheleire
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=20120928121758.GA2362@mail.sceen.net \
--to=rbraun@sceen.net \
--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