From: Daniel Barkalow <barkalow@iabervon.org>
To: Bruno Cesar Ribas <ribas@c3sl.ufpr.br>
Cc: "Julian Phillips" <julian@quantumfyre.co.uk>,
=?X-UNKNOWN?Q?Karl_Hasselstr=C3=B6m?= <kha@treskal.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
"Steven Grimm" <koreth@midwinter.com>,
git@vger.kernel.org
Subject: Re: Git / Subversion Interoperability
Date: Fri, 23 Mar 2007 18:11:22 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0703231758090.6485@iabervon.org> (raw)
In-Reply-To: <20070323193427.GA12126@c3sl.ufpr.br>
On Fri, 23 Mar 2007, Bruno Cesar Ribas wrote:
> I began to think about it... the idea to have a git-svnserver is to move from
> svn to git and get my dev team not to worry about the transition at the
> start, but it is a good idea to make people get moving to git idea of
> devlopment, right?
> Or the main idea is that we will have a group devloping under git repo and a
> group under svn-gateway for the same project? I don't see a point to have
> this! when a repo type is defined everyone must begin to understand that way,
> even if it was changed in the middle of the project.
It's been useful in the past (when Wine went from CVS to git) to make it
unnecessary for all developers to switch which software they're using at
the same time. With that particular project, it really went from having a
CVS repository and a git gateway to having a git repository and a CVS
gateway without users seeing a difference (except that the CVS access was
suddenly faster).
Then, of course, the git users were able to start making use of the more
flexible representation of history, since the official repository then
could represent it.
-Daniel
*This .sig left intentionally blank*
next prev parent reply other threads:[~2007-03-23 22:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 22:48 Git / Subversion Interoperability Bruno Cesar Ribas
2007-03-23 0:43 ` Shawn O. Pearce
2007-03-23 1:03 ` Julian Phillips
2007-03-23 1:24 ` Shawn O. Pearce
2007-03-23 1:36 ` Julian Phillips
2007-03-23 10:34 ` Karl Hasselström
2007-03-23 15:21 ` Bruno Cesar Ribas
2007-03-23 15:48 ` Karl Hasselström
2007-03-23 18:13 ` Julian Phillips
2007-03-23 19:34 ` Bruno Cesar Ribas
2007-03-23 22:05 ` David Lang
2007-03-23 22:11 ` Daniel Barkalow [this message]
2007-03-24 6:41 ` Shawn O. Pearce
2007-03-24 18:55 ` Karl Hasselström
2007-03-24 20:13 ` Linus Torvalds
2007-03-24 20:37 ` Junio C Hamano
2007-03-26 3:06 ` Sam Vilain
2007-03-23 21:30 ` Christian Wiese
2007-03-23 22:00 ` Steven Grimm
2007-03-24 6:56 ` Shawn O. Pearce
2007-03-26 3:04 ` Sam Vilain
2007-03-23 14:21 ` Jakub Narebski
2007-03-24 6:45 ` Shawn O. Pearce
2007-03-24 20:38 ` Eric Wong
2007-03-24 20:31 ` Eric Wong
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=Pine.LNX.4.64.0703231758090.6485@iabervon.org \
--to=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=julian@quantumfyre.co.uk \
--cc=kha@treskal.com \
--cc=koreth@midwinter.com \
--cc=ribas@c3sl.ufpr.br \
--cc=spearce@spearce.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 NNTP newsgroup(s).