From: Daniel Jacobowitz <drow@false.org>
To: binutils@sourceware.org
Subject: Re: svn read of the binutils development repository?
Date: Wed, 12 Apr 2006 14:02:00 -0000 [thread overview]
Message-ID: <20060412135823.GB23288@nevyn.them.org> (raw)
In-Reply-To: <20060412060641.GY13324@lug-owl.de>
On Wed, Apr 12, 2006 at 08:06:41AM +0200, Jan-Benedict Glaw wrote:
> If CVS is abandoned, why would SVN be choosen? For personal use, I'm
> using GIT these days and it's a nice experience.
Because (A) GCC uses it, and (B) it uses a familiar development
workflow to CVS.
This argument has been had in enough places, at enough times, I think.
Also, once switched to a changeset based system, moving to another
changeset based system is much less difficult. There's still some
doubt whether src should change at all, but I really don't feel we
need to debate what it would change to.
Doing live imports from SVN to GIT is probably not hard for folks
who would prefer to use GIT; in fact I see that svnimport already does
support it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-12 13:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 18:26 Christian Joensson
2006-04-10 15:44 ` Daniel Jacobowitz
2006-04-11 23:57 ` Ben Elliston
2006-04-12 6:06 ` Daniel Jacobowitz
2006-04-12 6:40 ` Jan-Benedict Glaw
2006-04-12 13:47 ` Paul Brook
2006-04-12 13:55 ` Paul Koning
2006-04-12 13:58 ` Daniel Jacobowitz
2006-04-12 13:58 ` Paul Koning
2006-04-12 15:12 ` Daniel Jacobowitz
2006-04-12 14:02 ` Daniel Jacobowitz [this message]
2006-05-09 14:17 ` Christian Joensson
2006-05-09 14:49 ` Daniel Jacobowitz
2006-08-08 14:31 ` Christian Joensson
2006-08-08 14:52 ` Daniel Jacobowitz
2006-08-08 16:59 ` Daniel Jacobowitz
2006-11-23 11:14 ` Christian Joensson
2006-04-12 13:05 Alessio.MASSARO
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=20060412135823.GB23288@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).