From: PAUL GILLIAM <pgilliam@us.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] signal trampoline frame cache corruption
Date: Tue, 14 Nov 2006 01:50:00 -0000 [thread overview]
Message-ID: <1163468626.3428.32.camel@dufur.beaverton.ibm.com> (raw)
In-Reply-To: <20061113190543.GA1720@nevyn.them.org>
Thanks Daniel
On Mon, 2006-11-13 at 14:05 -0500, Daniel Jacobowitz wrote:
> On Mon, Nov 13, 2006 at 10:50:34AM -0800, PAUL GILLIAM wrote:
> > I don't know what happened. I fixed the indentation problems introduced
> > by the patch.
> > I have attached the original patch it's self, with correct indentation.
>
> Thanks! Looks good this time. I fixed the formatting and date of the
> ChangeLog entry for you.
>
>
prev parent reply other threads:[~2006-11-14 1:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 19:41 patch: signal trampoline frame cache corruption (repost?) PAUL GILLIAM
2006-10-31 23:28 ` Mark Kettenis
2006-11-03 17:58 ` PAUL GILLIAM
2006-11-10 21:22 ` Daniel Jacobowitz
2006-11-13 17:42 ` [commit] signal trampoline frame cache corruption PAUL GILLIAM
2006-11-13 17:46 ` Daniel Jacobowitz
2006-11-13 18:57 ` PAUL GILLIAM
2006-11-13 19:05 ` Daniel Jacobowitz
2006-11-14 1:50 ` PAUL GILLIAM [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=1163468626.3428.32.camel@dufur.beaverton.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=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