Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Upstream bfd patch for ia64 vDSO support
Date: Fri, 03 Jun 2005 19:36:00 -0000	[thread overview]
Message-ID: <42A0B138.10300@redhat.com> (raw)
In-Reply-To: <20050603190957.GC32722@nevyn.them.org>



Daniel Jacobowitz wrote:
> On Wed, Jun 01, 2005 at 04:13:29PM -0400, Jeff Johnston wrote:
> 
>>The attached patch has been checked in to binutils by Jim Wilson.  It fixes 
>>a problem with the ia64 vDSO so that gdb can backtrace from system calls.  
>>I need this to check in an ia64/libunwind patch that fixes backtracing 
>>through syscalls.  I didn't know if one could just check in upstream bfd 
>>patches without approval so I will ask.  May I commit this?
> 
> 
> GDB and binutils live in the same source repository.  Applying it to
> one applies it to the other, except for release branches of course. 
> There's nothing more to do.
> 

Ok, thanks for the clarification.

-- Jeff J.


      reply	other threads:[~2005-06-03 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 20:13 Jeff Johnston
2005-06-03 19:10 ` Daniel Jacobowitz
2005-06-03 19:36   ` Jeff Johnston [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=42A0B138.10300@redhat.com \
    --to=jjohnstn@redhat.com \
    --cc=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