From: Andrew Sayers <andrew-git@pileofstuff.org>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Florian Achleitner <florian.achleitner2.6.31@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Ramkumar Ramachandra <artagnon@gmail.com>,
David Barr <davidbarr@google.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
Dmitry Ivankov <divanorama@gmail.com>
Subject: Re: GSOC Proposal draft: git-remote-svn
Date: Wed, 11 Apr 2012 23:43:43 +0100 [thread overview]
Message-ID: <4F86091F.7010800@pileofstuff.org> (raw)
In-Reply-To: <20120411195351.GG4248@burratino>
On 11/04/12 20:53, Jonathan Nieder wrote:
> [...]
>> Additionally the remote-helper will read a configuration file containing
>> additional information about branch-mapping, this should be closely related to
>> Andrew's SBL.
>
> That sounds reasonable to me. I am somewhat unconvinced (but
> convinceable) about the need to use a configuration scheme that
> handles all the edge cases right away. Shouldn't it be enough to tell
> the importer the following?
>
> - the path to the repository (from which it can deduce $SVNROOT
> and the path within there to the subproject of interest)
>
> - a single bit of information on top of that: "this repository uses
> the standard layout"
>
> Once that works, the tools could easily be tweaked to respect a
> configuration file that describes more complex situations, and as a
> bonus the SBL tools for making sense of those situations would have
> time to become more mature in the meantime.
SBL itself is just a plain text description of which directories are
branches etc. - there are a handful of tricky bits on Florian's side of
the fence, but it shouldn't be that hard to add everything necessary to
parse any arbitrary SBL file. For example, if he gets an SBL action
that looks like this:
In r105, create branch "/foo" as "foo-bar" from "/bar/baz" r25
... then the logic that produced that line doesn't really matter, so
long as he can convert it to a series of fast-import commands.
I started work on exporting branches from SVN a few months ago, and
happened to be polishing off SBL when GSoC got going, so my work ties
nicely into Florian's. I've been keen to talk about edge cases lately
because that's the point I'm at in my work - to make a long story short,
I know how to do the easy cases now, and need to veer off into some
weird edge cases for a month or two, before swinging back by the
standard layout and optimising for that. If Florian needs something
that generates SBL before I'm ready, I'd be happy to cobble a basic
"standard layout only" script from the modules I've got.
- Andrew
next prev parent reply other threads:[~2012-04-11 22:43 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 14:42 GSoC intro Florian Achleitner
2012-03-19 21:31 ` Andrew Sayers
2012-03-20 12:25 ` Florian Achleitner
2012-03-20 13:19 ` David Barr
2012-03-21 21:16 ` Florian Achleitner
2012-03-26 11:06 ` Ramkumar Ramachandra
2012-03-27 13:53 ` Florian Achleitner
2012-04-02 8:30 ` GSOC Proposal draft: git-remote-svn Florian Achleitner
2012-04-02 11:00 ` Ramkumar Ramachandra
2012-04-02 20:57 ` Jonathan Nieder
2012-04-02 23:04 ` Jonathan Nieder
2012-04-03 7:49 ` Florian Achleitner
2012-04-03 18:48 ` Jonathan Nieder
2012-04-05 16:18 ` Tomas Carnecky
2012-04-02 22:17 ` Andrew Sayers
2012-04-02 22:29 ` Jonathan Nieder
2012-04-02 23:20 ` Andrew Sayers
2012-04-03 0:09 ` Jonathan Nieder
2012-04-03 21:53 ` Andrew Sayers
2012-04-03 22:21 ` Jonathan Nieder
2012-04-05 13:36 ` Florian Achleitner
2012-04-05 15:47 ` Dmitry Ivankov
2012-04-09 18:59 ` Stephen Bash
2012-04-10 17:17 ` Jonathan Nieder
2012-04-10 22:30 ` Andrew Sayers
2012-04-10 23:46 ` Jonathan Nieder
2012-04-11 19:09 ` Florian Achleitner
2012-04-14 22:57 ` Andrew Sayers
2012-04-11 15:51 ` Jakub Narebski
2012-04-11 15:56 ` Jonathan Nieder
2012-04-11 19:20 ` Florian Achleitner
2012-04-11 19:44 ` Dmitry Ivankov
2012-04-11 19:53 ` Jonathan Nieder
2012-04-11 22:43 ` Andrew Sayers [this message]
2012-04-12 9:02 ` Thomas Rast
2012-04-12 15:28 ` Florian Achleitner
2012-04-12 22:30 ` Andrew Sayers
2012-04-14 20:09 ` Florian Achleitner
2012-04-14 21:35 ` Andrew Sayers
2012-04-15 3:13 ` Stephen Bash
2012-04-13 19:19 ` Jonathan Nieder
2012-04-14 20:15 ` Florian Achleitner
2012-04-18 20:16 ` Florian Achleitner
2012-04-19 12:26 ` Florian Achleitner
2012-03-28 8:09 ` GSoC intro Miles Bader
2012-03-28 9:30 ` Dmitry Ivankov
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=4F86091F.7010800@pileofstuff.org \
--to=andrew-git@pileofstuff.org \
--cc=artagnon@gmail.com \
--cc=davidbarr@google.com \
--cc=divanorama@gmail.com \
--cc=florian.achleitner2.6.31@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--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.
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).