From: Daniel Jacobowitz <drow@false.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: schwab@suse.de, gdb@sourceware.org
Subject: Re: How to avoid stepping inside libpthread
Date: Wed, 26 Sep 2007 21:06:00 -0000 [thread overview]
Message-ID: <20070926160650.GA28492@caradoc.them.org> (raw)
In-Reply-To: <20070713.160341.55513392.nemoto@toshiba-tops.co.jp>
On Fri, Jul 13, 2007 at 04:03:41PM +0900, Atsushi Nemoto wrote:
> Oh yes, thank you for suggestion. Here is an updated patch against
> current snapshot.
Hi Atsushi,
I'm sorry I never got back to you about this. I tried your patch
today and it seems to work. But do you have an FSF copyright
assignment, or are you planning on getting one? This is too
substantial for us to merge it without one.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-09-26 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 6:18 Atsushi Nemoto
2007-07-11 9:00 ` Andreas Schwab
2007-07-12 2:15 ` Atsushi Nemoto
2007-07-12 6:31 ` Atsushi Nemoto
2007-07-12 11:10 ` Daniel Jacobowitz
2007-07-13 7:04 ` Atsushi Nemoto
2007-09-26 21:06 ` Daniel Jacobowitz [this message]
2007-07-11 11:40 ` Daniel Jacobowitz
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=20070926160650.GA28492@caradoc.them.org \
--to=drow@false.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=gdb@sourceware.org \
--cc=schwab@suse.de \
/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