Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: Fix PR1659
Date: Thu, 06 Oct 2005 00:41:00 -0000	[thread overview]
Message-ID: <20051006004137.GA20186@nevyn.them.org> (raw)
In-Reply-To: <20051006003945.GM26007@bubble.grove.modra.org>

On Thu, Oct 06, 2005 at 10:09:45AM +0930, Alan Modra wrote:
> On Sun, Oct 02, 2005 at 06:27:32PM -0400, Daniel Jacobowitz wrote:
> > On Wed, Sep 28, 2005 at 05:11:18PM +0930, Alan Modra wrote:
> > > Obvious fixes.  OK to apply?
> > > 
> > > 	PR 1659
> > > 	* rs6000-tdep.c (rs6000_push_dummy_call): Correct size of
> > > 	backchain write.
> > > 	(rs6000_convert_from_func_ptr_addr): Correct comment
> > 
> > I can't get at gnatsweb at the moment to read the PR, but the fix
> > is definitely obvious.  OK.
> 
> Applied.  Would someone please close the bug report?  I don't have
> gnatsweb access.

Sure, done.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


      reply	other threads:[~2005-10-06  0:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28  7:41 Alan Modra
2005-10-02 22:27 ` Daniel Jacobowitz
2005-10-06  0:39   ` Alan Modra
2005-10-06  0:41     ` 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=20051006004137.GA20186@nevyn.them.org \
    --to=drow@false.org \
    --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