This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gcc development schedule [Re: sharing libcpp between GDB and GCC]
- From: Phil Edwards <phil at jaj dot com>
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Cc: zack at codesourcery dot com, gcc at gcc dot gnu dot org, gdb at sources dot redhat dot com, jimb at redhat dot com, rth at redhat dot com
- Date: Thu, 28 Mar 2002 15:15:00 -0500
- Subject: Re: gcc development schedule [Re: sharing libcpp between GDB and GCC]
- References: <200203280317.WAA05137@caip.rutgers.edu>
On Wed, Mar 27, 2002 at 10:17:03PM -0500, Kaveh R. Ghazi wrote:
> > From: Zack Weinberg <zack@codesourcery.com>
> >
> > I'll add that this is an argument for a better version control
> > system; most of the changes on the queue inside my head, I would
> > have done on a branch if CVS didn't make branches such a pain.
> > (E.g. it takes about 10x longer to do "cvs update" on the 3.0
> > branch than the trunk.)
> > zw
>
> Yeah, what's up with that? (I thought it was just me.)
I will point out that for doing more than a trivial number of cvs operations,
I saw a huge win after I started mirroring the CVS repository, and then
doing checkouts/updates/diffs from the local mirror. The only time I need
to explicitly talk to the server is for checkins.
Phil
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams