From: Ramkumar Ramachandra <artagnon@gmail.com>
To: David Michael Barr <davidbarr@google.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Dmitry Ivankov <divanorama@gmail.com>
Subject: Re: [linux.conf.au] VCS Interoperability
Date: Tue, 10 Jan 2012 14:18:17 +0530 [thread overview]
Message-ID: <CALkWK0kMmDMZ4wiMSmOfwBLzd+xBEA+WKsviu9FVcvj9eZEahg@mail.gmail.com> (raw)
In-Reply-To: <CAFfmPPMH2643JMMZdVbOQJL7DB-DiRYQS8x0TqEaSbGmhMdBNw@mail.gmail.com>
Hi David,
David Michael Barr wrote:
> Next week, I'll be presenting a summary of the past 2 years work
> on improving svn interoperability for git.
> I'm requesting feedback from anyone who cares with regard to
> what they'd like to hear about.
Nice. As a lay person attending the conference, here are a few things
I think I'd like to hear:
- Why this project is so challenging compared to say, a git-hg bridge
or a git-darcs bridge. What makes Subversion especially hard to deal
with?
- What is the biggest motivation for developing the svnrdump/ svnrload
combination? Are there any other usecases for the tools?
- How has this project contributed to the development of the
fast-import infrastructure? Can these changes be used to improve
other/ future remote helpers?
- You've spoken about exporting Subversion history to Git so far, but
what about the reverse? Which parts of the picture are still missing?
Thanks.
-- Ram
next prev parent reply other threads:[~2012-01-10 8:48 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 [this message]
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
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=CALkWK0kMmDMZ4wiMSmOfwBLzd+xBEA+WKsviu9FVcvj9eZEahg@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=davidbarr@google.com \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@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).