From: Jonathan Nieder <jrnieder@gmail.com>
To: David Barr <davidbarr@google.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Scott Chacon <schacon@gmail.com>,
Brian Gernhardt <benji@silverinsanity.com>,
david@lang.hm, Ramkumar Ramachandra <artagnon@gmail.com>,
git@vger.kernel.org, Dmitry Ivankov <divanorama@gmail.com>
Subject: Re: [PULL] svn-fe updates for master or next
Date: Fri, 27 Jan 2012 01:20:23 -0600 [thread overview]
Message-ID: <20120127072023.GB806@burratino> (raw)
In-Reply-To: <CAFfmPPN-g+Lk2n9tzXe=CfyK8OZ7nGu4NwX0cXjtxS0W7SwPHA@mail.gmail.com>
David Barr wrote:
> I do think we need to gather Dmitry's work on svn-fe
Listed at [1]. Thanks for the nice and well maintained overview,
Dmitry.
> and propose a
> front-end for core so that it is no longer relegated to contrib.
Yep. Should such a remote helper link directly to the vcs-svn lib, or
would it make sense to start with a script that makes use of svn-fe
(possibly with a different name once it is hoisted out of contrib)?
[1] http://divanorama.github.com/gsoc11/streams.html
next prev parent reply other threads:[~2012-01-27 7:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 12:30 [linux.conf.au] VCS Interoperability David Michael Barr
2012-01-10 8:48 ` Ramkumar Ramachandra
2012-01-22 3:39 ` David Michael Barr
2012-01-22 10:25 ` Ramkumar Ramachandra
2012-01-22 21:12 ` david
2012-01-22 23:33 ` Brian Gernhardt
2012-01-23 0:43 ` Scott Chacon
2012-01-26 23:47 ` David Barr
2012-01-27 0:10 ` Jonathan Nieder
2012-01-27 0:33 ` [PULL] svn-fe updates for master or next Jonathan Nieder
2012-01-27 0:46 ` Jonathan Nieder
2012-01-27 1:03 ` David Barr
2012-01-27 7:20 ` Jonathan Nieder [this message]
2012-01-27 18:39 ` Junio C Hamano
2012-01-28 4:37 ` Junio C Hamano
2012-01-27 18:50 ` Junio C Hamano
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=20120127072023.GB806@burratino \
--to=jrnieder@gmail.com \
--cc=artagnon@gmail.com \
--cc=benji@silverinsanity.com \
--cc=david@lang.hm \
--cc=davidbarr@google.com \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=schacon@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).