From: Andrew Sayers <andrew-git@pileofstuff.org>
To: Sam Vilain <sam@vilain.net>
Cc: Stephen Bash <bash@genarts.com>, Nathan Gray <n8gray@n8gray.org>,
Jonathan Nieder <jrnieder@gmail.com>, Jeff King <peff@peff.net>,
git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>,
Dmitry Ivankov <divanorama@gmail.com>,
Ramkumar Ramachandra <artagnon@gmail.com>,
David Barr <davidbarr@google.com>
Subject: Re: [spf:guess,iffy] Re: [spf:guess] Re: Approaches to SVN to Git conversion (was: Re: [RFC] "Remote helper for Subversion" project)
Date: Thu, 08 Mar 2012 20:51:44 +0000 [thread overview]
Message-ID: <4F591BE0.4070709@pileofstuff.org> (raw)
In-Reply-To: <4F57EC04.8060705@vilain.net>
Thanks - this has really helped my thoughts to crystalise.
Here's my plan at this point:
1. Create an "SVN History description" project
This will build on the ASCII format I've been proposing so far. The
goal will be to produce a human- and machine-readable format that
describes SVN history in terms of an idealised version control system;
and to produce a set of tests that any SVN history exporter can use as a
testing framework.
2. Create an SVN history exporter
This will build on the svn-branch-export.pl script I previously made
available. That script ran in exactly two passes ("configure" and
"make") which wrote pointlessly different file formats. The new script
will accept an SVN history file as input and create another SVN history
file as output, allowing users to iteratively improve the file as Sam
described.
3. Create an SVN history importer for git
This will resemble the git-branch-import.pl script I previously made
available, but written in C based on the final SVN history format. This
thread has convinced me this would be a nice little SoC project, and
I'll propose it in another thread if I've got project 1 to a reasonable
state before it's too late. Failing that, and if nobody else wants to
take this project, I'll have a go myself some day when project 2 is
approaching completion.
My next step will be to write up the SVN history work thrown up by this
thread. I'll come back to the list for advice when I've got something
presentable.
- Andrew
next prev parent reply other threads:[~2012-03-08 20:51 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
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 [this message]
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=4F591BE0.4070709@pileofstuff.org \
--to=andrew-git@pileofstuff.org \
--cc=artagnon@gmail.com \
--cc=bash@genarts.com \
--cc=davidbarr@google.com \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=n8gray@n8gray.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).