From: Eli Zaretskii <eliz@is.elta.co.il>
To: Mark Kettenis <kettenis@wins.uva.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Cleanup i386-tdep.c
Date: Sun, 18 Feb 2001 03:07:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010218130454.6713C-100000@is> (raw)
In-Reply-To: <200102181017.f1IAHmd11648@delius.kettenis.local>
On Sun, 18 Feb 2001, Mark Kettenis wrote:
> Which reminds me: where is the right place to put the x86 watchpoints
> stuff I'm working on? Is i386-tdep.c a good one? i386-nat.c doesn't
> seem to exist...
>
> Please create i386-nat.c (and i386-nat.h, for the exported
> interfaces).
Okay, will do. Thanks for the feedback.
next prev parent reply other threads:[~2001-02-18 3:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 15:06 Mark Kettenis
2001-02-17 22:23 ` Eli Zaretskii
2001-02-18 2:17 ` Mark Kettenis
2001-02-18 3:07 ` Eli Zaretskii [this message]
2001-02-18 12:34 ` Eli Zaretskii
[not found] ` <4331-Sun18Feb2001223249+0200-eliz@is.elta.co.il>
2001-02-19 8:03 ` Mark Kettenis
2001-02-19 10:47 ` Andrew Cagney
2001-02-19 14:03 ` Mark Kettenis
2001-02-19 14:46 ` Fernando Nasser
2001-03-17 14:31 [PATCH]: " Mark Kettenis
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=Pine.SUN.3.91.1010218130454.6713C-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@wins.uva.nl \
/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