Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [cagney_convert-20030606-branch] Merge with mainline
Date: Mon, 09 Jun 2003 22:06:00 -0000	[thread overview]
Message-ID: <20030609220559.GA1556@nevyn.them.org> (raw)
In-Reply-To: <3EE4FF8A.7000906@redhat.com>

On Mon, Jun 09, 2003 at 05:43:38PM -0400, Andrew Cagney wrote:
> Since Mark's managed to demonstrate that branch fixing the i386 store 
> bugs, I'd like to merge it into mainline.  To that end I'm thinking of 
> the following commit sequence for the mainline:
> 
> - deprecate register_convertible et.al.
> Mainly because I'd like to change register_convert_to_raw's function 
> signature so that the FROM buffer is made constant
> 
> - testcase
> 
> - the patch (will need to also update alpha)

Sounds reasonable to me.  One affected PR is gdb/214; I haven't checked
but from following the discussion I think this will fix that.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2003-06-09 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-09 21:43 Andrew Cagney
2003-06-09 22:06 ` Daniel Jacobowitz [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=20030609220559.GA1556@nevyn.them.org \
    --to=drow@mvista.com \
    --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