Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: GDB Patches ML <gdb-patches@sourceware.org>
Subject: Re: Ping, Re: Infinite backtrace on (eg.) ARM
Date: Thu, 05 Oct 2006 22:27:00 -0000	[thread overview]
Message-ID: <20061005222744.GB14087@nevyn.them.org> (raw)
In-Reply-To: <1160084996.9761.93.camel@localhost.localdomain>

On Thu, Oct 05, 2006 at 02:49:55PM -0700, Michael Snyder wrote:
> Ping, Daniel?  I was offering to do the work for you, of
> isolating and committing the 3rd part of the patch.  This
> would stop the infinite backtrace behavior, and would not
> be incompatible with what you intend when you get around 
> to finishing the work.

Sorry, as you can tell I'm way further backlogged than just to
mid-September in patch response.  Please give me a chance to
settle out the previous patch, and then maybe this can go in
as-is.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-10-05 22:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22  1:48 Michael Snyder
2006-09-22  2:59 ` Daniel Jacobowitz
2006-09-22 18:56   ` Michael Snyder
2006-10-05 21:51     ` Ping, " Michael Snyder
2006-10-05 22:27       ` Daniel Jacobowitz [this message]
2006-09-22 19:00 ` Jim Blandy

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=20061005222744.GB14087@nevyn.them.org \
    --to=drow@false.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