From: Stefan Sperling <stsp@elego.de>
To: Will Palmer <wmpalmer@gmail.com>
Cc: "Michael J Gruber" <git@drmicha.warpmail.net>,
"Ramkumar Ramachandra" <artagnon@gmail.com>,
"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: Wed, 14 Jul 2010 10:58:22 +0200 [thread overview]
Message-ID: <20100714085822.GC25630@jack.stsp.name> (raw)
In-Reply-To: <1278949191.1611.5.camel@wpalmer.simply-domain>
On Mon, Jul 12, 2010 at 04:39:51PM +0100, Will Palmer wrote:
> On Mon, 2010-07-12 at 17:24 +0200, Stefan Sperling wrote:
> > Regarding compilation, take a look at tools/dev/unix-build/Makefile.svn
> This is all moot, because the whole point is that svndumpr compiles
> against libsvn, so you don't need the whole svn source-tree.
It's not moot. svndumpr may now or in the future be using API calls which
are specific to the Subversion 1.7 libraries, in which case you'll need
to compile Subversion from trunk to get compatible libraries until
1.7 is released. Maybe Ramkumar wants to maintain a 1.6.x-specific
version you can use, but that won't be living in our repository anyway.
Stefan
next prev parent reply other threads:[~2010-07-14 8:58 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
2010-07-14 8:58 ` Stefan Sperling [this message]
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=20100714085822.GC25630@jack.stsp.name \
--to=stsp@elego.de \
--cc=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=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).