From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] libcap: fetch from Debian
Date: Thu, 23 Aug 2012 09:36:13 +0200 [thread overview]
Message-ID: <5035DD6D.8060205@linaro.org> (raw)
In-Reply-To: <20120823073139.GK3029@jama.jama.net>
W dniu 23.08.2012 09:31, Martin Jansa pisze:
> On Thu, Aug 23, 2012 at 09:24:29AM +0200, Marcin Juszkiewicz wrote:
>> Original location was kernel.org and it was not restored after server
>> was hacked.
>
> So the SRC_URI checksums are different because it was repackaged? Please
> include diff of content from those 2 archives in commit message.
Content of those archives is exactly same. Checked md5 sums of all file
in both.
next prev parent reply other threads:[~2012-08-23 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 7:24 [PATCH 1/2] subversion: update to 1.7.6 Marcin Juszkiewicz
2012-08-23 7:24 ` [PATCH 2/2] libcap: fetch from Debian Marcin Juszkiewicz
2012-08-23 7:31 ` Martin Jansa
2012-08-23 7:36 ` Marcin Juszkiewicz [this message]
2012-08-23 16:26 ` [PATCH 1/2] subversion: update to 1.7.6 Saul Wold
2012-08-24 9:47 ` Marcin Juszkiewicz
2012-08-24 18:49 ` Saul Wold
2012-08-24 19:21 ` Saul Wold
2012-08-27 15:56 ` Saul Wold
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=5035DD6D.8060205@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=martin.jansa@gmail.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