From: Alexander Gavrilov <angavrilov@gmail.com>
To: Mike Ralphson <mike.ralphson@gmail.com>
Cc: Chris Velevitch <chris.velevitch@gmail.com>, git@vger.kernel.org
Subject: Re: VSS to git
Date: Mon, 2 Mar 2009 21:55:31 +0300 [thread overview]
Message-ID: <200903022155.31771.angavrilov@gmail.com> (raw)
In-Reply-To: <e2b179460903020951h7f1538daya4d3cdb96fc7c65d@mail.gmail.com>
On Monday 02 March 2009 20:51:12 Mike Ralphson wrote:
> 2009/3/2 Chris Velevitch <chris.velevitch@gmail.com>:
> > I can't seem to find any utilities to convert a vss repository to git.
> > In the absence of such a tool, what is the best approach to converting
> > an vss repository to git?
>
> You might be able to two-stage through vss2svn[1], and from there to git.
> Or take the guts of vss2* [2] and rewrite the backend to create git
> fast-import format?
Last year I experimented with conversion using vss2svn plus a heavily
patched version of git-svnimport, and it worked quite well. The largest
problem is that VSS cannot record directory copies, so the resulting
SVN repository does not have them either. This makes conversion tools
unable to detect any branching, so I had to implement support for
completely arbitrary mapping specs.
I also made an incremental synchronization script for simple actions
(requires logging to be enabled in VSS).
Alexander
P.S: I made some fixes to vss2svn too, they are in a separate branch:
http://www.pumacode.org/projects/vss2svn/browser/branches/Alexander
next prev parent reply other threads:[~2009-03-02 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 17:15 VSS to git Chris Velevitch
2009-03-02 17:48 ` Michael J Gruber
2009-03-02 17:51 ` Mike Ralphson
2009-03-02 18:55 ` Alexander Gavrilov [this message]
2012-11-05 22:08 ` victorcruz
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=200903022155.31771.angavrilov@gmail.com \
--to=angavrilov@gmail.com \
--cc=chris.velevitch@gmail.com \
--cc=git@vger.kernel.org \
--cc=mike.ralphson@gmail.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;
as well as URLs for NNTP newsgroup(s).