public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: ac131313@localhost.cygnus.com (Andrew Cagney)
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: Ian Roxborough <irox@redhat.com>,
	gcc@gcc.gnu.org, insight@sources.redhat.com,
	gdb@sources.redhat.com
Subject: Re: Tcl/Tk update on the upgrade...
Date: Fri, 21 Sep 2001 10:02:00 -0000	[thread overview]
Message-ID: <20010921170209.DBF603E0B@localhost.cygnus.com> (raw)
In-Reply-To: <Pine.BSF.4.33.0109211233590.14009-100000@naos.dbai.tuwien.ac.at>

> On Thu, 20 Sep 2001, Ian Roxborough wrote:
> > things are looking a lot better with Tcl/Tk upgrade.
> 
> I'm utterly confused by those Tcl/Tk related messages of yours being
> sent to gcc@gcc.gnu.org.

GDB's and BINUTILS' combined CVS repository also contains a copy of
dejagnu, expect and tcl.  Creating a source tree containing that and
GCC and then testing it is a very common pratice (well I thought it
was until now).  Any changes Ian makes to tcl are going to directly
affect anyone using the src dejagnu to test GCC.

I suggested that Ian include gcc when posting updates so that all
interested parties were kept informed.

> What is "the Tcl/Tk" upgrade you're referring to, and is it really
> related to the (non-Redhat-internal) development of GCC?

Andrew

  reply	other threads:[~2001-09-21 10:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20 15:55 Ian Roxborough
2001-09-21  3:36 ` Gerald Pfeifer
2001-09-21 10:02   ` Andrew Cagney [this message]
     [not found] <200109211712.f8LHC7201923@constant.com>
2001-09-21 13:53 ` Phil Edwards
2001-09-21 17:12   ` Ian Roxborough
2001-09-24 10:12     ` Phil Edwards

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=20010921170209.DBF603E0B@localhost.cygnus.com \
    --to=ac131313@localhost.cygnus.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=irox@redhat.com \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).