From: Phil Muldoon <pmuldoon@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: time to be serious about dropping CVS
Date: Fri, 08 Jan 2010 12:58:00 -0000 [thread overview]
Message-ID: <4B472BDC.1030301@redhat.com> (raw)
In-Reply-To: <20100101080137.GP2788@adacore.com>
On 01/01/2010 08:01 AM, Joel Brobecker wrote:
> Hello everyone,
>
> Happy New Year!
>
> Since I started using SVN, and even more so since I started using git,
> I have found that using CVS is very inconvenient, bordering on unbearable.
Beyond the usual arguments and cons about CVS, the one thing that
really bites is that CVS always has to talk to a remote server. It is
not distributed, so there is no local repository copy. On a small
project that is ok, but currently diffs with GDB CVS take 12-15
minutes. Commits are the same. The same operations in GIT take
seconds. It is even worse in the US 8am - 6pm hours. This might be
because I live in the UK, and the server is on another continent.
Maybe folks closer to the server get a snappier response. But if
there was problem that a distributed version control system was meant
to fix, it was this.
I don't know why CVS is so slow. Whether it is CPU bound on the
sourceware machine, or the bandwidth at the hosting site is at
capacity .. who knows? I'm not even sure how to find out. But would
SVN solve any of the problem relating to performance?
My preference is for GIT, simply because of the speed.
Cheers,
Phil
next prev parent reply other threads:[~2010-01-08 12:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 8:02 Joel Brobecker
2010-01-01 8:35 ` Eli Zaretskii
2010-01-01 9:00 ` Joel Brobecker
2010-01-01 10:34 ` Eli Zaretskii
2010-01-01 15:39 ` Matthias Urlichs
2010-01-01 15:49 ` Eli Zaretskii
2010-01-01 10:26 ` Mark Kettenis
2010-01-01 10:46 ` Andreas Schwab
2010-01-01 11:03 ` Joel Brobecker
2010-01-01 16:06 ` Matthias Urlichs
2010-01-01 17:57 ` H.J. Lu
2010-01-01 13:00 ` Joseph S. Myers
2010-01-01 14:18 ` Joel Brobecker
2010-01-02 18:11 ` Christopher Faylor
2010-01-02 19:08 ` Christopher Faylor
2010-01-03 13:52 ` Matthias Urlichs
2010-01-08 12:58 ` Phil Muldoon [this message]
2010-01-08 13:08 ` Tristan Gingold
2010-01-08 13:20 ` Joel Brobecker
2010-01-08 13:26 ` Tristan Gingold
2010-01-08 13:13 ` Joel Brobecker
2010-01-08 13:21 ` Jonas Maebe
2010-01-08 13:34 ` Andreas Schwab
2010-01-08 13:14 ` Jonas Maebe
2010-01-08 18:41 ` Michael Snyder
2010-01-08 18:49 ` Paul Koning
2010-12-20 17:35 ` Joseph S. Myers
2010-12-21 3:27 ` Joel Brobecker
2010-12-21 3:46 ` Jim Blandy
2010-12-21 7:16 ` Pascal Obry
2010-12-21 15:14 ` Tom Tromey
2010-12-21 16:15 ` Christopher Faylor
2010-12-21 18:39 ` Joseph S. Myers
2010-12-21 19:26 ` Tom Tromey
2010-12-21 18:42 ` Joseph S. Myers
2010-12-21 19:21 ` DJ Delorie
2010-12-22 15:23 ` Christopher Faylor
2010-12-22 15:29 ` NightStrike
2010-12-22 16:48 ` Joseph S. Myers
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=4B472BDC.1030301@redhat.com \
--to=pmuldoon@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.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