From: Christopher Faylor <cgf@redhat.com>
To: overseers@gcc.gnu.org, gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: gcc development schedule [Re: sharing libcpp between GDB and GCC]
Date: Thu, 28 Mar 2002 21:29:00 -0000 [thread overview]
Message-ID: <20020329052913.GA22971@redhat.com> (raw)
In-Reply-To: <20020328090029.B55362@dragon.nuxi.com>
On Thu, Mar 28, 2002 at 09:00:29AM -0800, David O'Brien wrote:
>On Thu, Mar 28, 2002 at 01:53:46AM -0800, Jason Molenda 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.)
>>
>>The cvs server on sourceware uses an optimization (a patch written by
>>Ian Lance Taylor) to cache the information needed for a cvs update in a
>>single file per directory.
>
>How about a *REAL* optimization, such as not locking ,v files for
>anoncvs users??
The last time you suggested this, I offered to send you the source code
for the version of cvs that is being run on sources.redhat.com. And, I
suggested that if you would like to rebuild cvs, verify that it works,
and be available for bug reports for your changes, I'd be willing to
install your new cvs binary on the system.
Why haven't you taken me up on my offer?
cgf
next prev parent reply other threads:[~2002-03-29 5:29 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 [this message]
2002-03-28 9:00 ` David O'Brien
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=20020329052913.GA22971@redhat.com \
--to=cgf@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=overseers@gcc.gnu.org \
/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