From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFC] TLS support part 3
Date: Wed, 02 Oct 2002 07:53:00 -0000 [thread overview]
Message-ID: <20021002145410.GA22578@nevyn.them.org> (raw)
In-Reply-To: <15770.64626.434733.368375@localhost.redhat.com>
On Wed, Oct 02, 2002 at 10:02:26AM -0400, Elena Zannoni wrote:
>
> Last patch. These are the configure machinery changes.
> Pending resolution of the config.in diffs....(as posted on gdb@)
Well, half of those are the result of not rerunning autoheader; and the
other half are a known issue between two different versions of
autoconf/autoheader. So they look OK to me.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-10-02 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 7:04 Elena Zannoni
2002-10-02 7:53 ` Daniel Jacobowitz [this message]
2002-10-02 8:30 ` Elena Zannoni
2002-10-02 8:32 ` Daniel Jacobowitz
2002-11-11 18:41 ` Elena Zannoni
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=20021002145410.GA22578@nevyn.them.org \
--to=drow@mvista.com \
--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