From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: mtn disapprove
Date: Fri, 11 Jan 2008 09:30:08 +0100 [thread overview]
Message-ID: <fm79ef$hak$1@ger.gmane.org> (raw)
In-Reply-To: <47871C71.5020800@student.utwente.nl>
Koen Kooi schrieb:
> however instead of collie-2.6.inc you mean zaurus-2.6.inc.
of course. Sorry about the glitch. I believe I have made the correct
change in 6794aa0dd1ca646be71cc57651a883ac99f55985, now. Thanks for
spotting it.
While we are at it, let's try and clean the situation up a bit.
* Is there any reason not to let zaurus-2.6.inc do what it suggests to
be doing and delegate all clamshell stuff to zaurus-clamshell.inc?
poodle.conf already requires zaurus-2.6.inc despite not being a
clamshell model. Let's make the changes necessary so that collie
can require it as well and then delete the double entry for the
installkit code from collie-2.6.inc.
* I am pretty sure the poodle line in collie.conf is incorrect.
* poodle-2.6.inc seems to be unused, can it be dropped?
Koen, are these basically sane proposals? If so, I would prepare an mtn
diff for inspection before committing.
Regards
Rolf
next prev parent reply other threads:[~2008-01-11 8:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 7:36 mtn disapprove Koen Kooi
2008-01-11 8:30 ` Rolf Leggewie [this message]
2008-01-11 8:38 ` Koen Kooi
2008-01-11 16:53 ` Rolf Leggewie
2008-01-11 18:48 ` Rolf Leggewie
2008-01-11 19:20 ` Koen Kooi
2008-01-11 19:32 ` Rolf Leggewie
2008-01-11 23:22 ` Thomas Kunze
2008-01-12 10:39 ` Rolf Leggewie
2008-01-13 13:09 ` Thomas Kunze
2008-01-13 15:06 ` Rolf Leggewie
2008-01-13 16:30 ` Koen Kooi
2008-01-14 11:21 ` Florian Boor
2008-01-14 11:44 ` Rolf Leggewie
2008-01-11 19:36 ` Rolf Leggewie
2008-01-11 11:06 ` ohviey1
-- strict thread matches above, loose matches on Subject: below --
2008-01-11 20:57 QMan
2008-01-12 10:42 ` Rolf Leggewie
2008-01-12 11:41 ` Richard Purdie
2008-01-13 20:26 QMan
2008-01-28 13:51 ` Rolf Leggewie
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='fm79ef$hak$1@ger.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.