From: Doug Evans <dje@transmeta.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cgen@sources.redhat.com, sid@sources.redhat.com
Subject: Re: [RFC] New cpu --- Morpho ms1
Date: Thu, 16 Jun 2005 16:04:00 -0000 [thread overview]
Message-ID: <17073.41712.920235.625815@casey.transmeta.com> (raw)
In-Reply-To: <20050616154855.GF27067@redhat.com>
Frank Ch. Eigler writes:
> These are reasonable concerns in the abstract. Let's not insist on
> extra maintenance work on this old code until there is an indication
> that another of those 20 different apps shows up, or that gdb/sim will
> model delayed writes too.
I disagree. There is value in avoiding obviously bad code, especially
instances that set a bad precedent.
I seriously doubt a reasonable solution is non-trivial.
next prev parent reply other threads:[~2005-06-16 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 20:19 Dave Brolley
2005-06-13 14:55 ` Frank Ch. Eigler
2005-06-15 21:37 ` Dave Brolley
2005-06-15 21:46 ` Doug Evans
2005-06-16 14:22 ` Dave Brolley
2005-06-16 15:22 ` Frank Ch. Eigler
2005-06-16 15:42 ` Doug Evans
2005-06-16 15:49 ` Frank Ch. Eigler
2005-06-16 16:04 ` Doug Evans [this message]
2005-06-15 21:39 ` Dave Brolley
2005-06-14 10:25 ` Nick Clifton
2005-06-15 15:40 ` Dave Brolley
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=17073.41712.920235.625815@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=cgen@sources.redhat.com \
--cc=fche@redhat.com \
--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).