From: "Frank Ch. Eigler" <fche@redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: cgen@sources.redhat.com, sid@sources.redhat.com
Subject: Re: [RFC] New cpu --- Morpho ms1
Date: Thu, 16 Jun 2005 15:49:00 -0000 [thread overview]
Message-ID: <20050616154855.GF27067@redhat.com> (raw)
In-Reply-To: <17073.40390.435362.400645@casey.transmeta.com>
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
Hi -
On Thu, Jun 16, 2005 at 08:41:58AM -0700, Doug Evans wrote:
> [...]
> - adding specialized code can be "that bad" because without adequate
> commenting like "do as I say, not as I do", more and more such code
> creeps in over time
> - imagine if there's 20 different apps (as in (eq? APPLICATION mumble))
> all with their own little tweaks to rtl-c.scm
>
> Remove the appearance of the text "SID" from rtl-c.scm and parameterize
> the feature on something generic and I'd be happier.
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.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-16 15:49 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 [this message]
2005-06-16 16:04 ` Doug Evans
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=20050616154855.GF27067@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dje@transmeta.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).