From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANNOUNCE] Kconfig support
Date: Mon, 20 Apr 2009 15:23:23 -0400 [thread overview]
Message-ID: <200904201523.25737.vapier@gentoo.org> (raw)
In-Reply-To: <49ECC210.6000902@freescale.com>
On Monday 20 April 2009 14:42:24 Scott Wood wrote:
> Mike Frysinger wrote:
> > no one said otherwise. please read the thread context before chiming in.
> > if you had, you'd know that i was taking issue with the position of
> > "let's not do XXX in v1 because it exists in v2",
>
> I don't recall anyone advocating that position, other than your original
> inquiry ("i thought this was one of the points of u-boot-2?").
>
> You seem to be arguing with yourself. :-)
most recently, it's come up with (previous) kconfig/kbuild and the clock
changes. people (myself included) were hesitant to undertake big tasks by
virtue of v2 already solving it. so yes, i am in effect invalidating my
previous stances and in the process, attempting to elicit/vet other people's
opinions. seems we're all up to speed now though.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090420/7411f41a/attachment.pgp
next prev parent reply other threads:[~2009-04-20 19:23 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 15:39 [U-Boot] [ANNOUNCE] Kconfig support Grant Likely
2009-04-20 18:22 ` Mike Frysinger
2009-04-20 18:42 ` Scott Wood
2009-04-20 19:23 ` Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-18 16:25 Jean-Christophe PLAGNIOL-VILLARD
2009-04-18 18:29 ` Mike Frysinger
2009-04-18 18:54 ` Wolfgang Denk
2009-04-18 19:18 ` Mike Frysinger
2009-04-18 20:01 ` Wolfgang Denk
2009-04-19 19:50 ` Robert Schwebel
2009-04-20 4:56 ` Mike Frysinger
2009-04-20 6:52 ` Robert Schwebel
2009-04-20 13:49 ` Mike Frysinger
2009-04-20 14:04 ` Robert Schwebel
2009-04-20 14:42 ` Mike Frysinger
2009-04-20 14:53 ` Robert Schwebel
2009-04-20 15:04 ` Jerry Van Baren
2009-04-20 15:20 ` Mike Frysinger
2009-04-20 15:34 ` Sascha Hauer
2009-04-20 18:29 ` Mike Frysinger
2009-04-21 7:04 ` Robert Schwebel
2009-04-21 7:13 ` Daniel Stenberg
2009-04-21 14:40 ` Wolfgang Denk
2009-04-21 14:54 ` Robert Schwebel
2009-04-21 18:21 ` Sascha Hauer
2009-04-21 20:08 ` Wolfgang Denk
2009-04-21 22:30 ` Sascha Hauer
2009-04-21 23:12 ` Wolfgang Denk
2009-04-22 7:17 ` Robert Schwebel
2009-04-22 13:58 ` Wolfgang Denk
2009-04-22 10:27 ` Ladislav Michl
2009-04-22 8:53 ` Heiko Schocher
2009-04-22 13:25 ` Ladislav Michl
2009-04-22 14:11 ` Wolfgang Denk
2009-04-22 14:26 ` Jerry Van Baren
2009-04-23 9:13 ` Ladislav Michl
2009-04-21 23:34 ` Ladislav Michl
2009-04-20 19:17 ` Wolfgang Denk
2009-04-20 19:12 ` Wolfgang Denk
2009-04-19 19:48 ` Robert Schwebel
2009-04-19 21:59 ` Kumar Gala
2009-04-19 23:21 ` Sascha Hauer
2009-04-20 6:50 ` Robert Schwebel
2009-04-18 18:41 ` Wolfgang Denk
2009-04-19 16:38 ` Kumar Gala
2009-04-20 12:02 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-20 19:08 ` Wolfgang Denk
2009-04-20 19:58 ` Kumar Gala
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=200904201523.25737.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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