Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Steve Ellcey <sje@cup.hp.com>
To: gdb-patches@sourceware.org, binutils@sourceware.org,
		newlib@sourceware.org
Cc: nickc@redhat.com, pogma@thewrittenword.com, bonzini@gnu.org
Subject: Re: Updating libtool
Date: Mon, 29 Sep 2008 15:45:00 -0000	[thread overview]
Message-ID: <200809291544.m8TFisi10246@lucas.cup.hp.com> (raw)
In-Reply-To: <48E0D65A.3010801@redhat.com>

The new libtool has been checked in to the src tree and the necessary files
reconfigured.  Let me know if there are any problems.  The GCC and Src trees
should now be in sync.

Steve Ellcey
sje@cup.hp.com


       reply	other threads:[~2008-09-29 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48E0D65A.3010801@redhat.com>
2008-09-29 15:45 ` Steve Ellcey [this message]
2008-09-29 15:48   ` NightStrike
2008-09-29 16:56     ` H.J. Lu
2008-09-30  3:22       ` NightStrike
2008-09-26 20:25 sje

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=200809291544.m8TFisi10246@lucas.cup.hp.com \
    --to=sje@cup.hp.com \
    --cc=binutils@sourceware.org \
    --cc=bonzini@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=newlib@sourceware.org \
    --cc=nickc@redhat.com \
    --cc=pogma@thewrittenword.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