From: Mark Kettenis <kettenis@science.uva.nl>
To: dmj+@andrew.cmu.edu
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] The MIPS/Linux port
Date: Thu, 05 Jul 2001 02:12:00 -0000 [thread overview]
Message-ID: <200107050911.f659BG829924@debye.wins.uva.nl> (raw)
In-Reply-To: <20010704163423.A25013@nevyn.them.org>
Date: Wed, 4 Jul 2001 16:34:23 -0700
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Fixed. Do you see any other formatting problems?
Yep :-). It would be great if you could wrap the definitions of
REGISTER_U_ADDR and CANNOT_STORE_REGISTER such that the lines are not
too long for 80-character wide terminal.
Otherwise, things look really fine.
Mark
next prev parent reply other threads:[~2001-07-05 2:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010704121952.A17445@nevyn.them.org>
2001-07-04 14:51 ` H . J . Lu
2001-07-04 14:53 ` Mark Kettenis
2001-07-04 16:34 ` Daniel Jacobowitz
2001-07-05 2:12 ` Mark Kettenis [this message]
2001-07-05 16:57 ` John Court
2001-07-05 17:30 ` Daniel Jacobowitz
2001-07-05 17:45 ` John Court
2001-07-05 17:48 ` Daniel Jacobowitz
2001-07-04 23:48 ` Eli Zaretskii
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=200107050911.f659BG829924@debye.wins.uva.nl \
--to=kettenis@science.uva.nl \
--cc=dmj+@andrew.cmu.edu \
--cc=gdb-patches@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