From: "Frank Ch. Eigler" <fche@redhat.com>
To: Johan Rydberg <jrydberg@gnu.org>
Cc: sid@sources.redhat.com
Subject: Re: x86 full system simulation.
Date: Tue, 31 Oct 2006 14:56:00 -0000 [thread overview]
Message-ID: <20061031145557.GT4978@redhat.com> (raw)
In-Reply-To: <87lkmwy2u9.fsf@gnu.org>
Hi -
On Tue, Oct 31, 2006 at 03:30:54PM +0100, Johan Rydberg wrote:
> [...]
> "several years ago" is "nowdays" when it comes to the development pace
> of SID :)
Indeed, sid is stable, though Red Hat still undertakes some commercial
porting support for it.
> [...] Unrelated: Has anyone toyed with the idea of maybe throwing
> away mainDynamic+configrun and replacing it with a Python frontend?
> [...]
... or lua or something? It's all possible, and not hard to do.
(OTOH, disposing of prior front-ends is not necessary unless they are
well and truly supplanted.)
> I know that SID is somewhat hooked up to tcl, but I won't touch that
> with a three hundred meter pole.
Well, it wouldn't give you warts, if that's what you worry about. :-)
- FChE
prev parent reply other threads:[~2006-10-31 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 13:30 Johan Rydberg
2006-10-31 13:43 ` Frank Ch. Eigler
2006-10-31 14:30 ` Johan Rydberg
2006-10-31 14:56 ` Frank Ch. Eigler [this message]
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=20061031145557.GT4978@redhat.com \
--to=fche@redhat.com \
--cc=jrydberg@gnu.org \
--cc=sid@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).