From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joshua Lock <josh@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/2] Improve usability of checksums
Date: Mon, 24 Oct 2011 17:38:25 +0100 [thread overview]
Message-ID: <1319474305.26563.16.camel@ted> (raw)
In-Reply-To: <cover.1318352470.git.josh@linux.intel.com>
On Tue, 2011-10-11 at 10:07 -0700, Joshua Lock wrote:
> I'd heard some complaints around the usability of checksums and, having done
> some recipe work recently, must agree with them.
> This series ams to make using checksums less intrusive by:
>
> a) Removing the requirement that if one type of checksum is defined the other
> must be too.
> b) Reporting all sum mismatches at once
> c) Enabling sums to be defined as a parameter of a SRC_URI
>
> Regards,
> Joshua
>
> The following changes since commit dca46cc2e1c75b6add2c4801e2994a4812745f5b:
>
> fetch2: Export additional variables to the fetchers (2011-10-05 14:23:16 +0100)
>
> are available in the git repository at:
> git://github.com/incandescant/bitbake checksum
> https://github.com/incandescant/bitbake/tree/checksum
>
> Joshua Lock (2):
> fetch2: improve usability of checksums
> fetch2: enable checksum definition as SRC_URI parameter
Merged to master (or will be when I can actually push the changes).
Cheers,
Richard
prev parent reply other threads:[~2011-10-24 16:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 17:07 [PATCH 0/2] Improve usability of checksums Joshua Lock
2011-10-11 17:07 ` [PATCH 1/2] fetch2: improve " Joshua Lock
2011-10-12 19:21 ` Chris Larson
2011-10-13 12:49 ` Martin Jansa
2011-10-19 17:22 ` Joshua Lock
2011-10-11 17:07 ` [PATCH 2/2] fetch2: enable checksum definition as SRC_URI parameter Joshua Lock
2011-10-11 18:05 ` Khem Raj
2011-10-11 20:21 ` Joshua Lock
2011-10-11 17:19 ` [PATCH 0/2] Improve usability of checksums Scott Garman
2011-10-24 16:38 ` Richard Purdie [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=1319474305.26563.16.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=josh@linux.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