Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: PATCH: Add missing Morpho coprocessor registers
Date: Fri, 21 Apr 2006 18:50:00 -0000	[thread overview]
Message-ID: <44492958.7080909@redhat.com> (raw)
In-Reply-To: <uodyvv0pt.fsf@gnu.org>

Eli Zaretskii wrote:
>>Date: Thu, 20 Apr 2006 16:05:27 -0700
>>From: Michael Snyder <msnyder@redhat.com>
>>CC: gdb-patches@sourceware.org
>>
>>Should we mention the change in NEWS?
> 
> 
> If the added feature is something to die for, then yes.  But if
> normally users don't care about these registers, then it isn't
> important enough to be in NEWS.

I was more thinking about the change in target architecture name,
form ms1 to mt.


  reply	other threads:[~2006-04-21 18:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19  4:58 Mark Mitchell
2006-04-19 22:24 ` Kevin Buettner
2006-04-19 23:51   ` Daniel Jacobowitz
2006-04-20 23:05     ` Michael Snyder
2006-04-21  7:37       ` Eli Zaretskii
2006-04-21 18:50         ` Michael Snyder [this message]
2006-04-22  9:24           ` 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=44492958.7080909@redhat.com \
    --to=msnyder@redhat.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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