From: akuster808 <akuster808@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Armin Kuster <akuster808@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] lz4: update to version r123
Date: Sat, 08 Nov 2014 15:10:03 -0800 [thread overview]
Message-ID: <545EA2CB.9070600@gmail.com> (raw)
In-Reply-To: <CAJTo0La7oYuqFVBm7S3ta1mHxroYA_tJSV+f-s+PR+f+bGoywA@mail.gmail.com>
On 11/07/2014 04:00 AM, Burton, Ross wrote:
>
> On 1 October 2014 15:23, Armin Kuster <akuster808@gmail.com
> <mailto:akuster808@gmail.com>> wrote:
>
> Makefile md5sum changed since version is hardcode in it.
>
>
> In the future, changing the license checksum so that it only checksums
> the section of the Makefile that has the license instead of the entire
> file would mean it doesn't need to be updated. Then again the makefile
> is a strange choice of file to checksum, I'd have expected it to be
> checksuming the source.
I will make that change the next time I update or remove the check all
together.
- Armin
> Ross
>
>
prev parent reply other threads:[~2014-11-08 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 14:23 [PATCH] lz4: update to version r123 Armin Kuster
2014-11-07 12:00 ` Burton, Ross
2014-11-08 23:10 ` akuster808 [this message]
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=545EA2CB.9070600@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox