From: Ben Elliston <bje@wasabisystems.com>
To: Doug Evans <dje@transmeta.com>
Cc: cgen@sources.redhat.com
Subject: Re: machine generated documentation for cgen ports
Date: Fri, 13 Jun 2003 01:17:00 -0000 [thread overview]
Message-ID: <87fzmeu66v.fsf@sashimi.wasabisystems.com> (raw)
In-Reply-To: <16103.39988.792981.202713@casey.transmeta.com>
Doug Evans <dje@transmeta.com> writes:
> That's what's done now. I'm only using html tables so perhaps the
> result can be prettier.
Ah -- sorry, I overlooked that. It's not bad.
> btw, I think either the bottom row should print numbers in binary or
> perhaps even better would be to print another row with the constant
> values in binary.
Agreed.
Ben
prev parent reply other threads:[~2003-06-13 1:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 7:48 Doug Evans
2003-06-11 12:34 ` Ben Elliston
2003-06-11 15:50 ` Doug Evans
2003-06-11 20:53 ` Ben Elliston
2003-06-11 21:17 ` Doug Evans
2003-06-13 1:17 ` Ben Elliston [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=87fzmeu66v.fsf@sashimi.wasabisystems.com \
--to=bje@wasabisystems.com \
--cc=cgen@sources.redhat.com \
--cc=dje@transmeta.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).