Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org, binutils@sources.redhat.com
Subject: time to be serious about dropping CVS
Date: Fri, 01 Jan 2010 08:02:00 -0000	[thread overview]
Message-ID: <20100101080137.GP2788@adacore.com> (raw)

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.
But now that I'm making massive mechanical changes (Start of New Year
procedure), I am really having a hard time accepting it - Just to do a diff
in order to verify my changes took 11mins. Same for the commit.  Another
smaller diff aborted 2mins after I started it because I made a mistake
in the command line.

There is no reason why every contributor should be continuing to waste
more time because we're stuck with an outdated tool.

I am prepared to do whatever it takes to switch to either SVN or git.
The problem is that i don't know how to solve the one sticky issue
of partial-checkouts :-).

Right now, git is so much more powerful and fast, that I will personally
focus on a transition to git.  What I'd like to do is for a group of
motivated contributors to form a "task force" whose goal is to come up
with possible suggestions on how to transition, and then offer them up
for review, with pros and cons, to the maintainers of the affected
projects.  Target date - I'm thinking sometime during the summer,
maybe the GCC Summit? At the very latest, end of year 2010.

Anyone interested, please email me.

-- 
Joel


             reply	other threads:[~2010-01-01  8:02 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-01  8:02 Joel Brobecker [this message]
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
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=20100101080137.GP2788@adacore.com \
    --to=brobecker@adacore.com \
    --cc=binutils@sources.redhat.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