From: Tristan Gingold <gingold@adacore.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Phil Muldoon <pmuldoon@redhat.com>, gdb@sourceware.org
Subject: Re: time to be serious about dropping CVS
Date: Fri, 08 Jan 2010 13:26:00 -0000 [thread overview]
Message-ID: <24A3BE8F-4985-4682-AB96-23EFA02EA5CA@adacore.com> (raw)
In-Reply-To: <20100108132008.GQ4623@adacore.com>
On Jan 8, 2010, at 2:20 PM, Joel Brobecker wrote:
>> Sure. I now always work on gdb.git (from git mirror) but still use
>> CVS to do my commit. Using this approach makes the switch much less
>> necessary (IMHO).
>
> I disagree entirely. We're wasting time everytime someone does a commit.
> I think I spend about half a day doing the copyright year updates, and
> in the end, I decided to simply stop checking the diffs before doing
> the commit, since getting a diff was simply taking too much time.
> Regardless of what we end up choosing, there is no doubt in my mind
> that we must stop using CVS ASAP.
I agree. I should have said 'less urgent'. I also sympathize with the copyright year work.
> You guys also don't have to deal with branches, but branches just do
> not work neither with CVS, nor with SVN.
Yes, I agree. Back-porting is boring. For binutils I have a script that does the work from the
commit mail.
> I realize that this discussing might seem a little deja-vu and boring,
> so I'll stop now, and spend the energy on working on an alternative.
Good luck!
Tristan.
next prev parent reply other threads:[~2010-01-08 13:26 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
2010-01-08 13:08 ` Tristan Gingold
2010-01-08 13:20 ` Joel Brobecker
2010-01-08 13:26 ` Tristan Gingold [this message]
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=24A3BE8F-4985-4682-AB96-23EFA02EA5CA@adacore.com \
--to=gingold@adacore.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=pmuldoon@redhat.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