All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Iorga, Cristian" <cristian.iorga@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>,
	Martin Jansa <martin.jansa@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] libical: upgrade to 1.0.1
Date: Thu, 9 Jul 2015 15:57:02 +0000	[thread overview]
Message-ID: <969F26A8BAB325438E7EB80D3C3134FB44B12A9E@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <CAJTo0LYjQBPh1qBRvrasYTyknaVG+hKbxmS8kcFpRjrgrjgxKw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]

Hi all,

Hahaha. I am laughing because I assumed that the word “archive” means the file will stay there forever with the same checksum. Silly me. ☺
They have another link, but I am not sure if that stays up and that the checksum does not change.
Is this always true, that the checksum changes?

Thanks,
Cristian


From: Burton, Ross [mailto:ross.burton@intel.com]
Sent: Thursday, July 9, 2015 6:10 PM
To: Martin Jansa
Cc: Iorga, Cristian; OE-core
Subject: Re: [OE-core] [PATCH 2/2] libical: upgrade to 1.0.1


On 9 July 2015 at 15:32, Martin Jansa <martin.jansa@gmail.com<mailto:martin.jansa@gmail.com>> wrote:
aren't github archives regenerated from time to time with different
checksums?

Yes.  I keep on meaning to write a QA test for this. :)

Cristi - if this is the best libical has as a tarball release then we should do a proper git clone.  Amazingly, the download button on their website links to a tarball of master which is borderline reckless.

Ross

[-- Attachment #2: Type: text/html, Size: 5372 bytes --]

  reply	other threads:[~2015-07-09 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 14:28 [PATCH 0/2] BlueZ upgrades Cristian Iorga
2015-07-09 14:28 ` [PATCH 1/2] bluez5: upgrade to 5.32 Cristian Iorga
2015-07-09 14:28 ` [PATCH 2/2] libical: upgrade to 1.0.1 Cristian Iorga
2015-07-09 14:32   ` Martin Jansa
2015-07-09 15:09     ` Burton, Ross
2015-07-09 15:57       ` Iorga, Cristian [this message]
2015-07-09 16:04         ` Burton, Ross
2015-07-09 16:07           ` Iorga, Cristian
2015-07-09 16:09             ` Burton, Ross
2015-07-10 12:22       ` Martin Jansa

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=969F26A8BAB325438E7EB80D3C3134FB44B12A9E@irsmsx105.ger.corp.intel.com \
    --to=cristian.iorga@intel.com \
    --cc=martin.jansa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.