git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [GSoC] Git to SVN bridge
Date: Thu, 19 Apr 2012 17:56:59 -0500	[thread overview]
Message-ID: <20120419225659.GA4971@burratino> (raw)
In-Reply-To: <CALkWK0=7SPR-4Km5TUwg+rHm30aC7Uru9GJkkfYnL3OORV7nfg@mail.gmail.com>

Ramkumar Ramachandra wrote:

> Give 'vcs-svn/' the ability to spit out a Subversion dumpfile.  If you
> remember, we hit a brick wall last time when we needed a way to
> persist mark-referenced-blobs in the fast-import stream.

Yeah.  Ok, let's start there.

If I remember correctly, before we had this idea that svn-fi would be
a generic fast-import backend, so we could get support for pushing to
Subversion from other version control systems like Mercurial and RCS
for free.  An earlier idea was to use a very minimal subset of the
fast-import format.  You started with a patch that taught fast-export
a switch to produce that minimal subset, which was rejected because it
seemed like too much of a niche use case to be worth the cost to
compatibility.

However, that leaves whole swaths of the design space unexplored.  For
example, maybe "git fast-export" doesn't need to write the restricted
format but there would be a filter that takes an arbitrary fast-import
stream and converts it to the restricted thing.  Or maybe it would be
easiest to get something off the ground using that restricted
"fast-import lite" format and only afterwards expand svn-fi to handle
more commands so it can talk to the rest of the world.

In other words, if you are hitting a wall with that part which doesn't
seem to have much to do with differences between git and Subversion
anyway, I imagine there are easier places to start.  Alternatively, if
you prefer to work on making it easy for an importer to handle "ls"
and "cat" commands and mark references, I think our previous attempts
were misguided and we can do better. :)  What do you think?

Jonathan

  reply	other threads:[~2012-04-19 22:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 16:07 [GSoC] Git to SVN bridge Ramkumar Ramachandra
2012-04-18 20:10 ` Jonathan Nieder
2012-04-19  3:55   ` Ramkumar Ramachandra
2012-04-19 22:56     ` Jonathan Nieder [this message]
2012-04-20  3:51       ` Ramkumar Ramachandra
2012-04-23 18:06         ` 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=20120419225659.GA4971@burratino \
    --to=jrnieder@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    /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).