From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Riku Voipio <riku.voipio@linaro.org>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"patches@linaro.org" <patches@linaro.org>
Subject: Re: [PATCH 1/3] ltp: cleanup recipe
Date: Thu, 24 Oct 2013 08:36:45 +0100 [thread overview]
Message-ID: <1382600205.2744.31.camel@ted> (raw)
In-Reply-To: <CAAqcGHmA8JKz-LEZvN76HzViMwA1P0FtYWLgt0z4oztet0C6fA@mail.gmail.com>
On Tue, 2013-10-22 at 10:37 +0300, Riku Voipio wrote:
> On 22 October 2013 01:42, Khem Raj <raj.khem@gmail.com> wrote:
> > On Monday, October 21, 2013, Riku Voipio <riku.voipio@linaro.org> wrote:
> >> Cleanups for ltp:
> >>
> >> 1. Instead of using giturl like in Anders's patch use the sourceforge
> >> mirror URL.
> >
> > whats wrong with git url ?
>
> The previous LTP version in OE used to have tarball url, so I was just
> changing it back. I guess the main functional difference is that git
> url won't have checksums for downloads? Using tarball downloads over
> git checkouts is being more kind to upstream hosting. Mostly a matter
> of taste, or does OE-core have some preferred policy?
The recipe recently changed from using tarballs to using git. There was
a reason for it although offhand, I don't remember what it was. I think
it was mentioned on the list. I just looked at the commit and sadly it
wasn't mentioned there (it should have been). It would be good to decide
which approach the recipe should be using and stick with that...
Cheers,
Richard
prev parent reply other threads:[~2013-10-24 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 8:16 [PATCH 1/3] ltp: cleanup recipe Riku Voipio
2013-10-21 8:16 ` [PATCH 2/3] ltp: Fix aarch64 build Riku Voipio
2013-10-21 8:16 ` [PATCH 3/3] ltp: enable power management and realtime tests Riku Voipio
2013-10-21 22:42 ` [PATCH 1/3] ltp: cleanup recipe Khem Raj
2013-10-22 7:37 ` Riku Voipio
2013-10-22 9:34 ` Khem Raj
2013-10-24 7:36 ` 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=1382600205.2744.31.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=patches@linaro.org \
--cc=riku.voipio@linaro.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