git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: David Barr <davidbarr@google.com>
Cc: Jeff King <peff@peff.net>,
	git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>,
	Dmitry Ivankov <divanorama@gmail.com>,
	Ramkumar Ramachandra <artagnon@gmail.com>,
	Sam Vilain <sam@vilain.net>, Stephen Bash <bash@genarts.com>
Subject: Re: [RFC] "Remote helper for Subversion" project
Date: Sun, 4 Mar 2012 01:54:25 -0600	[thread overview]
Message-ID: <20120304075424.GI14725@burratino> (raw)
In-Reply-To: <CAFfmPPMPDCKjAmZ85Cj1cdT2yAUykm9sV6a66zXeFRmYfrmtjg@mail.gmail.com>

David Barr wrote:
> On Sat, Mar 3, 2012 at 11:27 PM, David Barr <davidbarr@google.com> wrote:

>> --- a/SoC-2012-Ideas.md
>> +++ b/SoC-2012-Ideas.md
>> @@ -182,3 +182,29 @@ this project.
>>
>>  Proposed by: Thomas Rast
>>  Possible mentor(s): Thomas Rast
>> +
>> +Remote helper for Subversion
>> +------------------------------------
>> +
>> +Write a remote helper for Subversion. While a lot of the underlying
>> +infrastructure work was completed last year, the remote helper itself
>> +is essentially incomplete. Major work includes:

By the way, didn't we have a remote-svn prototype?  I'm happy to merge
any old hacky thing for staging in contrib/svn-fe, as long as it is
not documented in a misleading way.

(More generally, if anyone wants to resend useful svn-fe patches, that
will help a lot.)

>> +
>> +* Understanding revision mapping and building a revision-commit mapper.

Does this mean creating commit notes to record which subversion rev
corresponds to each commit, and marks or lightweight tags going the
other way?

>> +
>> +* Working through transport and fast-import related plumbing, changing
>> +  whatever is necessary.

I think Dmitry and Sverre took care of most of this.

>> +
>> +* Getting an Git-to-SVN converter merged.

Probably could fill a summer in itself.  In previous starts I think
there was some complexity creep. :/

 http://thread.gmane.org/gmane.comp.version-control.git/170290
 http://thread.gmane.org/gmane.comp.version-control.git/170551

>> +
>> +* Building the remote helper itself.
>> +
>> +Goal: Build a full-featured bi-directional `git-remote-svn` and get it
>> +      merged into upstream Git.

Sure would be neat. ;-)  Another nice piece to build would be branch
tracking / follow_parent heuristics.

Thanks,
Jonathan

  reply	other threads:[~2012-03-04  7:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 12:27 [RFC] "Remote helper for Subversion" project David Barr
2012-03-03 12:41 ` David Barr
2012-03-04  7:54   ` Jonathan Nieder [this message]
2012-03-04 10:37     ` David Barr
2012-03-04 13:36       ` Andrew Sayers
2012-03-05 15:27         ` Approaches to SVN to Git conversion (was: Re: [RFC] "Remote helper for Subversion" project) Stephen Bash
2012-03-05 23:27           ` Approaches to SVN to Git conversion Andrew Sayers
2012-03-06 14:36             ` Stephen Bash
2012-03-06 19:29           ` Approaches to SVN to Git conversion (was: Re: [RFC] "Remote helper for Subversion" project) Nathan Gray
2012-03-06 20:35             ` Stephen Bash
2012-03-06 23:59               ` [spf:guess] " Sam Vilain
2012-03-07 22:06                 ` Andrew Sayers
2012-03-07 23:15                   ` [spf:guess,iffy] " Sam Vilain
2012-03-08 20:51                     ` Andrew Sayers
2012-03-06 22:34             ` Approaches to SVN to Git conversion Andrew Sayers
2012-03-07 15:38               ` Sam Vilain
2012-03-07 20:28                 ` Andrew Sayers
2012-03-07 22:33               ` Phil Hord
2012-03-07 23:08               ` Nathan Gray
2012-03-07 23:32                 ` Andrew Sayers
2012-03-04 16:23       ` [RFC] "Remote helper for Subversion" project Jonathan Nieder
2012-03-27  3:58     ` Ramkumar Ramachandra

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120304075424.GI14725@burratino \
    --to=jrnieder@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=bash@genarts.com \
    --cc=davidbarr@google.com \
    --cc=divanorama@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=sam@vilain.net \
    --cc=srabbelier@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).