From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
Cc: git@vger.kernel.org
Subject: Re: Errors importing Apache Synapse SVN using Git
Date: Fri, 11 Jul 2008 00:02:53 +0200 [thread overview]
Message-ID: <20080710220253.GD2325@atjola.homenet> (raw)
In-Reply-To: <g55130$n3i$1@ger.gmane.org>
On 2008.07.10 14:59:11 +0200, Michael J Gruber wrote:
> Asankha C. Perera venit, vidit, dixit 10.07.2008 14:01:
>> Hi All
>>
>> I am an Apache Synapse developer, and want to import the Synapse SVN
>> repo into Git, so that Ohloh can properly get the Synapse history
>> (http://www.ohloh.net/topics/1326?page=1#post_6287)
>>
>> However, when I try the command: "git svn clone --trunk=trunk
>> --tags=tags --branches=branches
>> http://svn.apache.org/repos/asf/synapse" it seems to take forever, (or
>> at least until the next network glitch), and keeps filling up a file
>> with just plain zeros ("0") :
>> ./.git/svn/trunk/.rev_db.13f79535-47bb-0310-9956-ffa450edef68
>>
>> Can someone try the above command on the Synapse repo and tell me what
>> I can do to import from the SVN?
>
> "svn log" takes forever on that repo, too. Current rev seems to be
> 675546, and the synapse path does not exist in early revisions. Knowing
> the initial revision would help, then you could save "git svn" from
> having to comb through (supposedly) tens of thousands of irrelevant revs.
>
> I just checked out trunk using svn 1.4.6, "svn log ." takes forever in
> the root dir. So the svn repo seems to be largely unusable, at least
> when accessed from svn 1.4.6 clients (the server is 1.5.0, I see).
>
> Okay, I bisected it and got r234477 as the beginning of time for
> synapse. "svn log -r 234477:HEAD" is still painful.
>
> You may want to fetch 1000 revs each or so from there each time.
Also, upgrading git to 1.5.6.2 might be a good idea. It doesn't use the
.revdb file format anymore, but a more efficient .revmap file. And it
has quite a few performance improvements (although they won't help
against the primary issue with that svn server). Don't use
1.5.6/1.5.6.1, they have a git-svn bug that can lead to corrupted clones
(just in case that your distro has packages for those versions but not
yet got 1.5.6.2).
Björn
next prev parent reply other threads:[~2008-07-10 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4875F5D6.9080906@wso2.com>
2008-07-10 12:01 ` Errors importing Apache Synapse SVN using Git Asankha C. Perera
2008-07-10 12:59 ` Michael J Gruber
2008-07-10 22:02 ` Björn Steinbrink [this message]
2008-07-11 11:54 ` Michael J Gruber
2008-07-14 8:16 ` Eric Wong
2008-07-14 9:14 ` Michael J Gruber
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=20080710220253.GD2325@atjola.homenet \
--to=b.steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=michaeljgruber+gmane@fastmail.fm \
/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