From: Markus Elfring <Markus.Elfring@web.de>
To: git@vger.kernel.org
Subject: Re: Speed of conversion from Subversion repository to Git
Date: Tue, 02 Feb 2010 12:20:35 +0100 [thread overview]
Message-ID: <4B680A83.80200@web.de> (raw)
In-Reply-To: <4B6717DF.8020004@web.de>
Hello,
The execution of the command "svn2git http://svn.opensuse.org/svn/yast/" was finished today somewhere during the night. I used the version 1.3.1 together with Git 1.6.6.1 on my openSUSE 11.2 system. Now I hope that my conversion try was really successful.
elfring@Sonne:~/Projekte/YaST/lokal> du -hs .git . && git branch
518M .git
653M .
Moblin
REFACTORING-10_3
SuSE-Code-11-Branch
SuSE-Code-11-SP1-Branch
SuSE-Linux-10_0-Branch
SuSE-Linux-10_1-Branch
SuSE-Linux-10_1-Branch@30668
SuSE-Linux-10_2-Branch
SuSE-Linux-10_3-Branch
SuSE-Linux-11_0-Branch
SuSE-Linux-11_2-Branch
SuSE-Linux-9_3-Branch
SuSE-SLE-10-Branch
SuSE-SLE-10-SP1-Branch
SuSE-SLE-10-SP1-Features-Branch
SuSE-SLE-10-SP2-Branch
SuSE-SLE-10-SP3-Branch
YaST2-X11-2-13-SuSE-10-1
YaST2-X11-2-13-SuSE-10-1@29086
YaST2-X11-2-14-SuSE-10-2
YaST2-X11-2-14-SuSE-10-2@34577
* master
moblin
research
selection_widgets_cleanup-core
selection_widgets_cleanup-core@22138
selection_widgets_cleanup-qt
selection_widgets_cleanup-qt@22138
tmp
unsupported
The network activity was mostly low during this lengthy process. Are more software developers interested to speed this procedure up?
Do know ways to improve the processor utilisation so that such a data import will be completed faster?
Regards,
Markus
next prev parent reply other threads:[~2010-02-02 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 18:05 Speed of conversion from Subversion repository to Git Markus Elfring
2010-02-01 18:17 ` Jacob Helwig
2010-02-02 11:20 ` Markus Elfring [this message]
2010-02-11 17:10 ` Markus Elfring
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=4B680A83.80200@web.de \
--to=markus.elfring@web.de \
--cc=git@vger.kernel.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).