From: Ian Lance Taylor <ian@cygnus.com>
To: joel@OARcorp.com
Cc: egcs@cygnus.com
Subject: Re: 970901 - cross problem with libio/gen-params
Date: Wed, 03 Sep 1997 10:33:00 -0000 [thread overview]
Message-ID: <199709031733.NAA22340@subrogation.cygnus.com> (raw)
In-Reply-To: <Pine.BSF.3.96.970903122707.28307A-100000@vespucci.advicom.net>
Date: Wed, 3 Sep 1997 12:30:48 -0500 (CDT)
From: Joel Sherrill <joel@OARcorp.com>
> When the egcs CVS server is up and running, I hope to start putting
> the development binutils releases on it as well. At that time, it
> will be possible to get a single consistent tree.
Does this mean that we will eventually be looking at egcs being a full
toolset tree?
Well, I hope that it means we will eventually be looking at the CVS
server being able to provide a full toolset tree. I doubt the whole
thing will ever be wrapped up into a single snapshot--it would be
rather large.
Ian
next prev parent reply other threads:[~1997-09-03 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-03 10:08 Joel Sherrill
1997-09-03 10:16 ` Ian Lance Taylor
1997-09-03 10:30 ` Joel Sherrill
1997-09-03 10:33 ` Ian Lance Taylor [this message]
1997-09-03 12:07 ` Joel Sherrill
1997-09-03 13:06 ` David Bristow
1997-09-03 13:36 ` Joel Sherrill
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=199709031733.NAA22340@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=egcs@cygnus.com \
--cc=joel@OARcorp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).