From: Sverre Rabbelier <srabbelier@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Sam Vilain <sam@vilain.net>,
David Michael Barr <david.barr@cordelta.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Update on SoC proposal: git-remote-svn
Date: Tue, 13 Apr 2010 18:01:55 +0200 [thread overview]
Message-ID: <l2yfabb9a1e1004130901z19db3392kbbd4d975a5d439f7@mail.gmail.com> (raw)
In-Reply-To: <1271136573-sup-5613@kytes>
Heya,
On Tue, Apr 13, 2010 at 07:29, Ramkumar Ramachandra <artagnon@gmail.com> wrote:
> Hm, this is something that I hadn't thought about earlier. Thanks for
> the suggestion- I will not attempt to go into complicated cases,
> atleast in my summer term.
I think we can safely say that "git clone svn://example.com/myrepo"
only has to work for svn repositories that have a 'sane' layout. If
you want a non-standard layout you can do 'git init && git configure
.... && git fetch', where you configure everything the way you want
before fetching. We could perhaps even provide a tool to aid with
configuring things; or perhaps a mode to not do any rewriting (just
import the data into git as-is) and then have a tool that examines the
history and interactively helps you set up an appropriate rewrite
config? Interesting times are ahead :).
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-04-13 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 5:29 Update on SoC proposal: git-remote-svn Ramkumar Ramachandra
2010-04-13 8:34 ` Sam Vilain
2010-04-13 16:01 ` Sverre Rabbelier [this message]
2010-04-14 6:33 ` Steven Michalske
2010-04-14 12:52 ` David Michael Barr
2010-04-14 17:15 ` David Michael Barr
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=l2yfabb9a1e1004130901z19db3392kbbd4d975a5d439f7@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=artagnon@gmail.com \
--cc=david.barr@cordelta.com \
--cc=git@vger.kernel.org \
--cc=sam@vilain.net \
/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).