From: Denys Dmytriyenko <denis@denix.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] image_types: use compress framework to produce checksums for images
Date: Thu, 14 Apr 2016 16:16:08 -0400 [thread overview]
Message-ID: <20160414201608.GF16135@denix.org> (raw)
In-Reply-To: <CAJTo0LY-OG4PL20oQA_KLwR+SxwtrUQjnzsPefGDRUUKZ0TJkA@mail.gmail.com>
On Thu, Apr 14, 2016 at 08:53:29PM +0100, Burton, Ross wrote:
> On 10 April 2016 at 19:49, Denys Dmytriyenko <denis@denix.org> wrote:
>
> > BTW, at least for md5sum (not sure about sha*), isn't the de-facto standard
> > extension .md5 and not .md5sum? Can we change it?
>
> Picking a random upstream (https://download.gnome.org/sources/glib/2.10/)
> shows that GNOME used .md5sum until they migrated over to sha256sum, so I'm
> not sure there's a de-facto standard as two equally reasonable options.
Hmm, ok. I guess with the migration to sha256sum, it's becoming to provide
multiple checksum files and I see more uses of .md5sum extension now. Never
mind, I'll update my infrastructure from the old .md5 days... :)
--
Denys
prev parent reply other threads:[~2016-04-14 21:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 20:16 [PATCH] image_types: use compress framework to produce checksums for images Alexander D. Kanevskiy
2016-03-24 20:28 ` Burton, Ross
2016-03-24 20:32 ` Andre McCurdy
2016-03-24 20:45 ` Alexander Kanevskiy
2016-03-24 21:14 ` Andre McCurdy
2016-04-10 18:49 ` Denys Dmytriyenko
2016-04-14 18:33 ` Denys Dmytriyenko
2016-04-14 19:53 ` Burton, Ross
2016-04-14 19:59 ` Otavio Salvador
2016-04-14 20:12 ` Denys Dmytriyenko
2016-04-14 20:31 ` Otavio Salvador
2016-04-14 21:26 ` Denys Dmytriyenko
2016-04-14 20:16 ` Denys Dmytriyenko [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=20160414201608.GF16135@denix.org \
--to=denis@denix.org \
--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