From: Michael Haggerty <mhagger@alum.mit.edu>
To: Marco Schulze <marco.c.schulze@gmail.com>
Cc: "James R. McKaskill" <james@foobar.co.nz>, git@vger.kernel.org
Subject: Re: [RFC 0/2] svn-fetch|push - an alternate approach
Date: Tue, 21 Aug 2012 09:06:20 +0200 [thread overview]
Message-ID: <5033336C.4050906@alum.mit.edu> (raw)
In-Reply-To: <5030BE33.9000007@gmail.com>
On 08/19/2012 12:21 PM, Marco Schulze wrote:
>
> 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.
Using libsvn would also have the benefit of letting the Subversion
project worry about forwards and backwards compatibility if the protocol
ever changes. (They tend to be quite diligent about that.)
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2012-08-21 7:13 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 ` [RFC 0/2] svn-fetch|push - an alternate approach Marco Schulze
2012-08-21 7:06 ` Michael Haggerty [this message]
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=5033336C.4050906@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=james@foobar.co.nz \
--cc=marco.c.schulze@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).