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: Mon, 23 Apr 2012 13:06:08 -0500 [thread overview]
Message-ID: <20120423180607.GF9635@burratino> (raw)
In-Reply-To: <CALkWK0mdzWQRY=fSmyML1p7352c7Lb3vuYoJd+TXSdTmFX1teg@mail.gmail.com>
Ramkumar Ramachandra wrote:
> I'm a little more worried about the mapper- I'm finding it hard
> to imagine a fast-import stream that contains subdirectories
> (branches/*) as opposed to head refs. Any idea how we'll achieve
> that?
Shouldn't it be very simple? All you need is a filter that understands
the fast-import syntax and can convert
commit refs/heads/topic
...
M 100644 inline "foo/bar"
to
commit toplevel
...
M 100644 inline "branches/topic/foo/bar"
and
ls topic@1 "foo/bar"
to
ls r1 "branches/topic/foo/bar"
prev parent reply other threads:[~2012-04-23 18:06 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
2012-04-20 3:51 ` Ramkumar Ramachandra
2012-04-23 18:06 ` Jonathan Nieder [this message]
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=20120423180607.GF9635@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).