public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@delorie.com>
To: nsd@redhat.com
Cc: gdb@sources.redhat.com, kettenis@wins.uva.nl
Subject: Re: Register cache
Date: Mon, 12 Feb 2001 10:37:00 -0000	[thread overview]
Message-ID: <200102121837.NAA07780@indy.delorie.com> (raw)
In-Reply-To: <200102121753.f1CHr9t11723@rtl.cygnus.com>

> Date: Mon, 12 Feb 2001 12:53:09 -0500
> From: Nick Duffek <nsd@redhat.com>
> 
> In my opinion, interface expansion is preferable to code duplication, so I
> agree with your patch to put i387_supply_fpreg in i387-nat.c. 

Thanks for the feedback.

> However,
> that's really a coding philosophy issue, and since Mark wrote i387-nat.c,
> I'm inclined to bow to his opinion on how it gets changed.

Perhaps Mark could take your opinion into consideration ;-).

  reply	other threads:[~2001-02-12 10:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-10 14:37 Mark Kettenis
2001-02-11 12:07 ` Nick Duffek
2001-02-11 23:26   ` Eli Zaretskii
2001-02-12  9:46     ` Nick Duffek
2001-02-12 10:37       ` Eli Zaretskii [this message]
2001-02-16 15:21         ` Mark Kettenis
2001-02-17  0:28           ` Eli Zaretskii
2001-02-17  3:19             ` Mark Kettenis
2001-02-13 13:38 ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2000-08-31  5:50 Register Cache Peter Reilley
2000-08-24 17:01 Wrong PC after external interrupt Fabrice Gautier
2000-08-29 18:01 ` Register Cache Steven Johnson
2000-08-30 21:40   ` Steven Johnson
2001-03-26  6:46   ` Andrew Cagney
2001-03-26  7:22     ` Fernando Nasser
     [not found]       ` <3ABFD062.17EDADAF@neurizon.net>
2001-03-29 16:27         ` Andrew Cagney
2001-03-29 16:27         ` Fernando Nasser

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=200102121837.NAA07780@indy.delorie.com \
    --to=eliz@delorie.com \
    --cc=gdb@sources.redhat.com \
    --cc=kettenis@wins.uva.nl \
    --cc=nsd@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).