Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] libpcre: Update to 8.35 version
Date: Mon, 19 May 2014 12:38:58 -0500	[thread overview]
Message-ID: <537A41B2.9000406@windriver.com> (raw)
In-Reply-To: <CAMKF1sqhEE0HOqLZ9nQ=vUQQeCYw4eCxLTTG7-036vsmqS5TCA@mail.gmail.com>

On 5/19/14, 12:31 PM, Khem Raj wrote:
> On Sun, May 18, 2014 at 10:36 PM, Chong Lu <Chong.Lu@windriver.com> wrote:
>> -LIC_FILES_CHKSUM = "file://LICENCE;md5=0920cc1a9f7ba95464491fa83c86afd8"
>> +LIC_FILES_CHKSUM = "file://LICENCE;md5=ded617e975f28e15952dc68b84a7ac1a"
>
> what changed ?
>

I just checked, and the only diff I can see is copyright 'years' were updated to 
include 2014.

--Mark


  reply	other threads:[~2014-05-19 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19  5:36 [PATCH 0/1] libpcre: Update to 8.35 version Chong Lu
2014-05-19  5:36 ` [PATCH 1/1] " Chong Lu
2014-05-19 17:31   ` Khem Raj
2014-05-19 17:38     ` Mark Hatle [this message]
2014-05-20  0:55       ` Khem Raj

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=537A41B2.9000406@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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