From: Eli Zaretskii <eliz@elta.co.il>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: [RFC] Non-executable stack on SPARC
Date: Mon, 26 Jan 2004 06:51:00 -0000 [thread overview]
Message-ID: <u8yjv2obs.fsf@elta.co.il> (raw)
In-Reply-To: <20040125235913.GA5120@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 25 Jan 2004 18:59:13 -0500)
> Date: Sun, 25 Jan 2004 18:59:13 -0500
> From: Daniel Jacobowitz <drow@mvista.com>
>
> I think just the patch you included will be OK.
Not surprising, since you were happy with it back in October, when
this issue was first raised.
next prev parent reply other threads:[~2004-01-26 6:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 23:50 Mark Kettenis
2004-01-25 23:59 ` Daniel Jacobowitz
2004-01-26 6:51 ` Eli Zaretskii [this message]
2004-01-26 6:51 ` Eli Zaretskii
2004-01-26 12:42 ` Mark Kettenis
2004-01-27 8:16 ` Eli Zaretskii
2004-02-01 17:48 ` Mark Kettenis
2004-02-01 20:13 ` Eli Zaretskii
2004-02-02 18:37 ` Andrew Cagney
2004-01-26 16:21 ` Andrew Cagney
2004-01-27 8:00 ` Eli Zaretskii
2004-02-01 17:54 ` Mark Kettenis
2004-02-02 18:27 ` Andrew Cagney
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=u8yjv2obs.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=drow@mvista.com \
--cc=gdb@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