From: "David O'Brien" <obrien@FreeBSD.org>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: overseers@gcc.gnu.org, Zack Weinberg <zack@codesourcery.com>,
gcc@gcc.gnu.org, gdb@sources.redhat.com, jimb@redhat.com
Subject: Re: gcc development schedule [Re: sharing libcpp between GDB and GCC]
Date: Thu, 28 Mar 2002 09:00:00 -0000 [thread overview]
Message-ID: <20020328085814.A55362@dragon.nuxi.com> (raw)
In-Reply-To: <Pine.BSF.4.44.0203281016560.83412-100000@pulcherrima.dbai.tuwien.ac.at>; from pfeifer@dbai.tuwien.ac.at on Thu, Mar 28, 2002 at 10:22:49AM +0100
On Thu, Mar 28, 2002 at 10:22:49AM +0100, Gerald Pfeifer wrote:
> On Wed, 27 Mar 2002, Zack Weinberg wrote:
> >>> (E.g. it takes about 10x longer to do "cvs update" on the 3.0
> >>> branch than the trunk.)
> >> Yeah, what's up with that? (I thought it was just me.)
>
> Same here.
>
> On the gcc-3.1 branch, I'm approaching the situation where cvs update
> takes longer than bootstrapping the compiler (with C and C++ frontends).
That is only because one must go across the network to do 'cvs up'.
When are public CVSup servers going to be made available? A bootstrap on
a fast machine takes 30 minutes. It does not take anywhere near that
long to 'cvs up' GCC from a local repository.
For those not wanting a local copy of the repository, CVSup in "check out
mode" (gives same results as 'cvs co' or 'cvs up' is 4x faster than
using CVS directly).
--
-- David (obrien@FreeBSD.org)
next prev parent reply other threads:[~2002-03-28 17:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 19:17 Kaveh R. Ghazi
2002-03-27 19:46 ` Zack Weinberg
2002-03-28 1:24 ` Gerald Pfeifer
2002-03-28 1:53 ` Jason Molenda
2002-03-28 2:01 ` Jason Molenda
2002-03-28 7:17 ` Christopher Faylor
2002-03-28 9:01 ` David O'Brien
2002-03-28 21:29 ` Christopher Faylor
2002-03-28 9:00 ` David O'Brien [this message]
2002-04-03 14:19 ` Jim Blandy
2002-04-03 14:29 ` Phil Edwards
2002-03-28 12:34 ` Phil Edwards
-- strict thread matches above, loose matches on Subject: below --
2002-03-27 6:01 Robert Dewar
2002-03-25 15:40 sharing libcpp between GDB and GCC Jim Blandy
2002-03-25 20:07 ` Zack Weinberg
2002-03-26 14:29 ` gcc development schedule [Re: sharing libcpp between GDB and GCC] Richard Henderson
2002-03-26 14:37 ` David Edelsohn
2002-03-26 21:32 ` Andreas Jaeger
2002-03-26 15:17 ` Neil Booth
2002-03-26 15:30 ` Tom Lord
2002-03-26 15:40 ` David Edelsohn
2002-03-26 16:03 ` Tom Lord
2002-03-26 16:41 ` Tim Hollebeek
2002-03-26 22:23 ` Eli Zaretskii
2002-03-26 22:43 ` Tom Lord
2002-03-27 7:18 ` mike stump
2002-03-27 9:00 ` law
2002-03-27 10:13 ` Neil Booth
2002-03-26 22:45 ` Tom Lord
2002-03-26 23:11 ` Daniel Berlin
2002-03-26 23:53 ` Tom Lord
2002-03-27 4:32 ` Fergus Henderson
2002-03-27 6:30 ` Andrew Cagney
2002-03-27 6:43 ` Gianni Mariani
2002-03-26 22:39 ` Andreas Jaeger
2002-03-26 22:54 ` Tom Lord
2002-03-26 15:31 ` Zack Weinberg
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=20020328085814.A55362@dragon.nuxi.com \
--to=obrien@freebsd.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=overseers@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
--cc=zack@codesourcery.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