git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
	Jonathan Nieder <jrnieder@gmail.com>,
	David Michael Barr <david.barr@cordelta.com>,
	Daniel Shahaf <daniel@shahaf.name>, Sam Vilain <sam@vilain.net>
Subject: [GSoC update extra!] git-remote-svn: Week 9
Date: Fri, 2 Jul 2010 23:57:52 +0200	[thread overview]
Message-ID: <20100702215752.GD2306@debian> (raw)

Hi,

I figured that I haven't posted a recent update about the RA
svnclient, so here it is. The good news is that using a combination of
trial-and-error and twisted logic, I seem to have to fix the memory
leaks and pool lifetime issues. I also managed to ouput the
text-content-length header by writing the dump to a temporary file and
stat'ing it. Unfortunately, the headers are still malformed, and this
requires some more work to get right. The client runs successfully and
manages to dump 5000 revisions of the ASF repository:

11.34s user 3.50s system 21% cpu 1:07.69 total

That's about 75 revisions per second, which isn't too bad I hope. This
is over the network, and my internet connection isn't all that fast.

The bad news is that the client seems to signal SIGABRT when it
finishes its work for some strange reason. Fortunately, I suspect that
this is a trivial issue where I'm leaking some error or forgetting to
clean up something. Hopefully, I'll be able to resolve this and fix
the dump headers within the next few days. After that, I'll scrub the
history clean and roll a series.

-- Ram

             reply	other threads:[~2010-07-02 21:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02 21:57 Ramkumar Ramachandra [this message]
2010-07-03  8:36 ` [GSoC update extra!] git-remote-svn: Week 9 Tay Ray Chuan
2010-07-03 19:47   ` Ramkumar Ramachandra

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=20100702215752.GD2306@debian \
    --to=artagnon@gmail.com \
    --cc=daniel@shahaf.name \
    --cc=david.barr@cordelta.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=sam@vilain.net \
    --cc=srabbelier@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).