From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Will Palmer <wmpalmer@gmail.com>
Cc: "Stefan Sperling" <stsp@elego.de>,
"Michael J Gruber" <git@drmicha.warpmail.net>,
"Git Mailing List" <git@vger.kernel.org>,
"Sverre Rabbelier" <srabbelier@gmail.com>,
"Greg Stein" <gstein@gmail.com>,
"Daniel Shahaf" <d.s@daniel.shahaf.name>,
"David Michael Barr" <david.barr@cordelta.com>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Bert Huijben" <rhuijben@collab.net>,
"Sam Vilain" <sam@vilain.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [GSoC update] git-remote-svn: Week 11
Date: Mon, 12 Jul 2010 20:12:33 +0200 [thread overview]
Message-ID: <20100712181233.GC17630@debian> (raw)
In-Reply-To: <1278949191.1611.5.camel@wpalmer.simply-domain>
Hi,
Will Palmer writes:
> This is all moot, because the whole point is that svndumpr compiles
> against libsvn, so you don't need the whole svn source-tree. All you
> need to get svndumpr working are some header files and a working libsvn.
> Everyone who currently uses git-svn already has a working libsvn, since
> perl's svn bindings wrap around libsvn anyway.
Yes, I meant that people will need the complete Subversion tree if I
DON'T get svnrdump merged somewhere in git.git (I'll attempt to get
the version that compiles against libsvn 1.6 merged). The instructions
to checkout the right branches and place it in the git tree can be
complicated: git-remote-svn relies on a chain of tools including
David's exporter and svnrdump to work.
-- Ram
next prev parent reply other threads:[~2010-07-12 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 14:35 [GSoC update] git-remote-svn: Week 11 Ramkumar Ramachandra
2010-07-12 14:48 ` Michael J Gruber
2010-07-12 15:24 ` Stefan Sperling
2010-07-12 15:39 ` Will Palmer
2010-07-12 18:12 ` Ramkumar Ramachandra [this message]
2010-07-14 8:58 ` Stefan Sperling
2010-07-12 16:00 ` 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=20100712181233.GC17630@debian \
--to=artagnon@gmail.com \
--cc=avarab@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=david.barr@cordelta.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gstein@gmail.com \
--cc=jrnieder@gmail.com \
--cc=rhuijben@collab.net \
--cc=sam@vilain.net \
--cc=srabbelier@gmail.com \
--cc=stsp@elego.de \
--cc=wmpalmer@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).