From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Brendan J Simon <brendan.simon@bigpond.com>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: [kbuild-devel] Re: linux kernel conf 0.8
Date: Wed, 9 Oct 2002 07:34:04 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.33L2.0210090730450.1001-100000@dragon.pdx.osdl.net> (raw)
In-Reply-To: <3DA43C3A.2060608@bigpond.com>
On Thu, 10 Oct 2002, Brendan J Simon wrote:
| Roman Zippel wrote:
|
| >>But the fact that xconfig depends on QT is going to make some people hate
| >>it.
| >>
| >>
| >This should be rather easily fixable, but it has to be done by someone who
| >is more familiar with whatever prefered toolkit. I'm familiar with QT and
| >it's absolutely great to get quickly reasonable results, if someone wants
| >something else I gladly will help, but I can't do it myself.
| >The interface to the back end is quite simple so it should be no real
| >problem to add a different user interface.
| >
|
| This is a difficult one. GUI's toolkits are a bit of religion
| (fundamentalist types too).
|
[good descriptions snipped]
|
| I'm pretty sure there is no one solution and it comes down to the
| politics and preferences of the final decision makers up the heirarchy.
|
| Good luck,
stick with TCL/TK, like xconfig currently uses ?
or is it not sufficient? or just too ugly?
--
~Randy
"In general, avoiding problems is better than solving them."
-- from "#ifdef Considered Harmful", Spencer & Collyer, USENIX 1992.
next prev parent reply other threads:[~2002-10-09 14:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0210081830350.4396-100000@home.transmeta.com>
2002-10-09 12:01 ` linux kernel conf 0.8 Roman Zippel
2002-10-09 13:35 ` Jeff Garzik
2002-10-09 13:55 ` Roman Zippel
2002-10-09 14:07 ` Jeff Garzik
2002-10-09 14:14 ` [kbuild-devel] " Brendan J Simon
2002-10-09 14:28 ` Jeff Garzik
2002-10-09 14:24 ` Brendan J Simon
2002-10-09 14:34 ` Randy.Dunlap [this message]
2002-10-09 14:45 ` J.A. Magallon
2002-10-09 15:14 ` Roman Zippel
2002-10-09 15:16 ` Linus Torvalds
2002-10-09 15:19 ` Randy.Dunlap
2002-10-09 16:29 ` Roman Zippel
2002-10-09 16:40 ` Christoph Hellwig
2002-10-09 18:39 ` Roman Zippel
2002-10-09 18:52 ` Peter Samuelson
2002-10-09 19:28 ` Randy.Dunlap
2002-10-09 19:39 ` Sam Ravnborg
2002-10-09 19:47 ` Randy.Dunlap
2002-10-09 14:55 ` [kbuild-devel] " Roman Zippel
2002-10-09 17:16 ` Sam Ravnborg
2002-10-09 17:37 ` Linus Torvalds
2002-10-09 17:55 ` Sam Ravnborg
2002-10-09 18:47 ` Linus Torvalds
2002-10-09 19:26 ` Sam Ravnborg
2002-10-09 20:41 ` Jeff Garzik
2002-10-09 22:49 ` Roman Zippel
2002-10-10 14:18 ` Jeff Garzik
2002-10-10 17:29 ` Sam Ravnborg
2002-10-10 17:32 ` Jeff Garzik
2002-10-10 17:51 ` Sam Ravnborg
2002-10-09 23:49 ` [kbuild-devel] " Brendan J Simon
2002-10-09 18:35 ` Jeff Garzik
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=Pine.LNX.4.33L2.0210090730450.1001-100000@dragon.pdx.osdl.net \
--to=rddunlap@osdl.org \
--cc=brendan.simon@bigpond.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).