From: Marco Schulze <marco.c.schulze@gmail.com>
To: "James R. McKaskill" <james@foobar.co.nz>
Cc: git@vger.kernel.org
Subject: Re: [RFC 0/2] svn-fetch|push - an alternate approach
Date: Sun, 19 Aug 2012 07:21:39 -0300 [thread overview]
Message-ID: <5030BE33.9000007@gmail.com> (raw)
In-Reply-To: <1345311556-70767-1-git-send-email-james@foobar.co.nz>
On 18-08-2012 14:39, James R. McKaskill wrote:
> As a twist the code does not use the svn library, but rather talks the
> svn protocol directly. I actually found it much easier to go this route
> then trying to bend everything to how the svn library understands
> things. It also has the advantage of not depending on libsvn. A number
> of distributions currently distribute the svn specific parts of git
> seperately to avoid this dependency.
It is a bit of a pain to work with libsvn, but I think it is worth using
it, not only due to protocol support, but also due to ready-to-use
support for SVN deltas and dumps. Pipelining could be implemented by
maintaining a set of connections (svn_ra_session_t structures) and
manually distributing work between them.
next prev parent reply other threads:[~2012-08-19 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 17:39 [RFC 0/2] svn-fetch|push - an alternate approach James R. McKaskill
2012-08-18 17:39 ` [RFC 1/2] add svn-fetch/push James R. McKaskill
2012-08-18 17:39 ` [RFC 2/2] add tests for git svn-fetch|push James R. McKaskill
2012-08-19 10:21 ` Marco Schulze [this message]
2012-08-21 7:06 ` [RFC 0/2] svn-fetch|push - an alternate approach Michael Haggerty
2012-08-22 2:30 ` James McKaskill
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=5030BE33.9000007@gmail.com \
--to=marco.c.schulze@gmail.com \
--cc=git@vger.kernel.org \
--cc=james@foobar.co.nz \
/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).