From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: script to remove orphaned files
Date: Thu, 16 Sep 2010 14:36:57 -0700 [thread overview]
Message-ID: <4C928DF9.2050405@mentor.com> (raw)
In-Reply-To: <AANLkTiko_vEXjjW+SUrvb=V+R-Vu0p3AvN7hcdD+Ghjg@mail.gmail.com>
Frans Meulenbroeks wrote:
> The patches I just pushed are tested using bitbake -c patch for all
> recipes as far as possible).
> (in the recipes I pushed I could not test alsa-scenario_git.bb as it
> didn't fetch for me and alsa-driver_0.9.6-hh4c.bb as it was for h3600
> and h3900 only),
Not to stop the work here, but is there a reason you couldn't do
MACHINE=h3600 bitbake -c patch -b
openembedded/recipes/alsa/alsa-driver_0.9.6-hh4c.bb ? Yes, the initial
parsing sucks but I think it's important for things like this to go out
and find the case where a given recipe is supposed to work and make sure
it still works. "It didn't fetch" is a legitimate stopper (and I think
candidate for moving to nonworking) of testing something.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-09-16 21:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 20:19 script to remove orphaned files Frans Meulenbroeks
2010-08-23 21:08 ` Khem Raj
[not found] ` <AANLkTi=s9gHBx_uPgiPGhu9b7D10JGytQaxyd-SZ+sfQ@mail.gmail.com>
2010-08-24 13:57 ` Chris Larson
2010-08-24 16:55 ` Frans Meulenbroeks
2010-09-13 20:20 ` Frans Meulenbroeks
2010-09-13 20:42 ` Khem Raj
2010-09-13 21:15 ` Frans Meulenbroeks
2010-09-13 21:23 ` Philip Balister
2010-09-16 20:56 ` Frans Meulenbroeks
2010-09-16 21:36 ` Tom Rini [this message]
2010-09-17 6:14 ` Frans Meulenbroeks
2010-09-17 15:19 ` Tom Rini
2010-09-17 17:03 ` Frans Meulenbroeks
2010-09-17 17:04 ` Frans Meulenbroeks
2010-10-11 20:49 ` 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=4C928DF9.2050405@mentor.com \
--to=tom_rini@mentor.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox