Re: GSOC Proposal draft: git-remote-svn

[Florian Achleitner <florian.achleitner2.6.31@gmail.com>]

Hi!

I'm curiously watching the discussion I kicked off with my proposal. Before 
refining the proposal I think I will let the discussion continue at the moment.
But just to clarify some things:
You know I'm rather new to this topic. I've used svn and git, I know what git 
plumbing is about, but I haven't used plumbing commands to write something 
into git yet. So I can't tell from experience if it would be good or not, 
compared to fast-import.
So please explain what's the advantage/disadvantage of which design decision.
That makes it easier to get the point.

I'm also not yet familiar with svn's internals and what properties they use 
for what. 
So there are several questions I simply don't have an answer for.
I know that you have discussed several issues in a huge lot of mails on this 
list. I'm watching and learning currently.

Jonathan wrote about a script "floating around". What's that?
Is it somewhere in a tree in some repo, is at a patch somewhere in a mail on 
the list, is it in git.git in some branch?? 
How does one find catch floating scripts?

And two clarifications about what I meant in the proposal:

On Monday 02 April 2012 16:30:14 Ramkumar Ramachandra wrote:
> Are you planning to extend svn-fe to do the mapping, write it as a
> separate program, or write it into the remote helper? I personally
> don't mind if the mapping is done in Perl (like in git-svn or SBL) as
> opposed to C; mapping is just parse-intensive.

I personally don't like Perl. :p (I would use python if i need a scripting 
language).
As far as I've seen, svn-fe is a 5-liner calling functions in vcs-svn/. So I 
thought there is no point of piping something through svn-fe in the remote-
helper. I thought I would use those functions like svn-fe does.
I thought about vcs-svn/ being a library for svn interaction that the remote-
helper, and svn-fe, and svn-fi (?) are using.

On Monday 02 April 2012 15:57:00 Jonathan Nieder wrote:
> Florian Achleitner wrote:
> Because of the above:
> > 1. Write a new bi-directional remote helper in C.
> 
> The word "new" makes me worried that you'd be throwing away whatever
> work already exists. :)

Probably I missed something. 
But all I've seen that is directly a remote-helper is a bash script which 
basically calls a pipeline from svnrdump | svn-fe | fast-import [2]. 
I'm not planning to write a longer program in bash. (I personally use bash 
only for things that fit on one terminal height).

Bash and Perl are not my favourites ;)

[1] https://github.com/divanorama/git/blob/remote-svn-alpha_v2/contrib/svn-
fe/git-remote-svn-alpha

Cheers,
Florian