git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Peter Baumann <waste.manager@gmx.de>,
	Jonathan Nieder <jrnieder@gmail.com>,
	David Barr <david.barr@cordelta.com>,
	Sverre Rabbelier <srabbelier@gmail.com>,
	Erik Faye-Lund <kusmabite@gmail.com>,
	Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/5] Towards a Git to SVN bridge
Date: Tue, 29 Mar 2011 23:43:07 +0530	[thread overview]
Message-ID: <1301422392-21177-1-git-send-email-artagnon@gmail.com> (raw)

Hi,

Thanks to Jonathan, Junio, Peter, and Erik among others for reviewing
previous iterations of this series. This iteration should take care of
most error handling and design issues addressed in the previous
iterations- it also comes along with a battery of tests.

Small introduction: svn-fi's design is modelled after git-fast-import.
It aims to be more comprehensive and production-ready than the
existing alternative, git2svn.  It converts a fast-import stream
to a Subversion dumpfile which can be loaded using `svnadmin load` (or
alternatively using `svnrdump load`, which will feature in Subversion
1.7).  The shortcomings can be summarized as follows:
1. dir_cache is a very naive implementation using string_list.  This
will not scale well either in memory or time, and should be replaced
with a prefix tree in future.
2. It currently only supports one branch. For supporting multiple
branches, two things need to be implemented: a branch-specific
dir_cache, and a mapper that maps branch names to directories (if the
standard "trunk", "branches", "tags" layout is not to be hardcoded).
3. Tags are currently unsupported, although it should be trivial to
implement once a mapping is in place.
4. Merges are unsupported.  This requires more thought.
5. The `from` command in the fast-import stream is ignored.  This
should probably be implemented like branching.
6. The data can't make round trips back-and-fourth yet.  Although this
topic has been discussed at length, there is no implementation of this
yet.

Thanks for reading.

-- Ram

Ramkumar Ramachandra (5):
  date: Expose the time_to_tm function
  fast-export: Introduce --inline-blobs
  strbuf: Introduce strbuf_fwrite corresponding to strbuf_fread
  vcs-svn: Introduce svnload, a dumpfile producer
  t9012-svn-fi: Add tests for svn-fi

 .gitignore                        |    1 +
 Documentation/git-fast-export.txt |    5 +
 Makefile                          |    6 +-
 builtin/fast-export.c             |   23 ++-
 cache.h                           |    1 +
 contrib/svn-fe/.gitignore         |    1 +
 contrib/svn-fe/Makefile           |   23 ++-
 contrib/svn-fe/svn-fi.c           |   16 +
 contrib/svn-fe/svn-fi.txt         |   28 ++
 date.c                            |    2 +-
 strbuf.c                          |   11 +
 strbuf.h                          |    1 +
 t/t9012-svn-fi.sh                 |  705 +++++++++++++++++++++++++++++++++++++
 test-svn-fi.c                     |   17 +
 vcs-svn/dir_cache.c               |   52 +++
 vcs-svn/dir_cache.h               |   11 +
 vcs-svn/dump_export.c             |  164 +++++++++
 vcs-svn/dump_export.h             |   26 ++
 vcs-svn/svnload.c                 |  485 +++++++++++++++++++++++++
 vcs-svn/svnload.h                 |   19 +
 20 files changed, 1591 insertions(+), 6 deletions(-)
 create mode 100644 contrib/svn-fe/svn-fi.c
 create mode 100644 contrib/svn-fe/svn-fi.txt
 create mode 100755 t/t9012-svn-fi.sh
 create mode 100644 test-svn-fi.c
 create mode 100644 vcs-svn/dir_cache.c
 create mode 100644 vcs-svn/dir_cache.h
 create mode 100644 vcs-svn/dump_export.c
 create mode 100644 vcs-svn/dump_export.h
 create mode 100644 vcs-svn/svnload.c
 create mode 100644 vcs-svn/svnload.h

-- 
1.7.4.rc1.7.g2cf08.dirty

             reply	other threads:[~2011-03-29 18:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 18:13 Ramkumar Ramachandra [this message]
2011-03-29 18:13 ` [PATCH 1/5] date: Expose the time_to_tm function Ramkumar Ramachandra
2011-03-29 18:13 ` [PATCH 2/5] fast-export: Introduce --inline-blobs Ramkumar Ramachandra
2011-03-29 20:44   ` Jonathan Nieder
2011-03-29 18:13 ` [PATCH 3/5] strbuf: Introduce strbuf_fwrite corresponding to strbuf_fread Ramkumar Ramachandra
2011-03-31  2:15   ` Jonathan Nieder
2011-03-29 18:13 ` [PATCH 4/5] vcs-svn: Introduce svnload, a dumpfile producer Ramkumar Ramachandra
2011-03-29 18:13 ` [PATCH 5/5] t9012-svn-fi: Add tests for svn-fi Ramkumar Ramachandra
2011-03-31 23:23   ` Jonathan Nieder

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=1301422392-21177-1-git-send-email-artagnon@gmail.com \
    --to=artagnon@gmail.com \
    --cc=david.barr@cordelta.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=kusmabite@gmail.com \
    --cc=srabbelier@gmail.com \
    --cc=waste.manager@gmx.de \
    /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).