From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: some more non fetching recipes
Date: Mon, 27 Sep 2010 06:49:10 -0500 [thread overview]
Message-ID: <4CA084B6.4070404@mwester.net> (raw)
In-Reply-To: <AANLkTimQJUyZRsX6a5EA4FruiM5DVVbVD8e676Ri+ARe@mail.gmail.com>
On 9/27/2010 1:19 AM, Frans Meulenbroeks wrote:
> 2010/9/26 Martin Jansa <martin.jansa@gmail.com>:
>
>> There was about ~1000 recipes failing to fetch few months ago, I don't
>> think this number is that much lower as I haven't seen any changes in
>> most of them.
>>
>> See my download status:
>> http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-April/019206.html
>> http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-April/019234.html
>
> April is 5 months ago. Question is if it makes sense to keep recipes
> that are broken for > 5 months and no one who saw a need to fix them
> or complained about them.
> Personally I'm inclined to say it is a waste to spend any time on
> these. I would suggest moving them to e.g. nonworking but I guess the
> people who mix up quality and quantity will disagree on this.
Mix up quality and quantity? That's a gross mischaracterization on your
part, and I quite resent it.
There are valid reasons for some of those. If it is now necessary to
make Mr. Jansa like the comments on the ixp4xx firmware recipe in order
to keep the recipe in OE, I will update those. But I cannot make it so
that Intel will not require click-throughs in order to download the
firmware files.
-Mike (mwester)
next prev parent reply other threads:[~2010-09-27 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 10:21 some more non fetching recipes Frans Meulenbroeks
2010-09-26 11:13 ` Holger Freyther
2010-09-26 11:58 ` Frans Meulenbroeks
2010-09-26 11:27 ` Martin Jansa
2010-09-26 12:14 ` Frans Meulenbroeks
2010-09-27 6:19 ` Frans Meulenbroeks
2010-09-27 11:49 ` Mike Westerhof [this message]
2010-09-27 12:51 ` Frans Meulenbroeks
2010-09-27 13:04 ` Martin Jansa
2010-10-03 11:46 ` Martin Jansa
2010-10-03 12:15 ` Frans Meulenbroeks
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=4CA084B6.4070404@mwester.net \
--to=mike@mwester.net \
--cc=openembedded-devel@lists.openembedded.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 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.