From: Richard Dallaway <dallaway@gmail.com>
To: Steven Michalske <smichalske@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: SVN bridge for multiple SVN modules
Date: Wed, 14 Apr 2010 13:43:15 +0100 [thread overview]
Message-ID: <v2ye3041f5c1004140543w11a16b48ye3095b266c0bc9b1@mail.gmail.com> (raw)
In-Reply-To: <236FD58B-CE33-4C06-A3AC-FD7DA7593EEB@gmail.com>
On Wed, Apr 14, 2010 at 7:08 AM, Steven Michalske <smichalske@gmail.com> wrote:
> On Apr 13, 2010, at 12:34 AM, Richard Dallaway wrote:
> Would setting up two git repositories cloning the SVN from the module_a and
> module_b directories and then making them as a git submodules is a git super
> project repository?
Thank you - I'll take a look at that.
I'm surprised that the "git svn clone
--ignore-paths=/everything_except_the_two_I-Want/" doesn't solve the
problem: I don't understand why it doesn't, and would love to
understand this better if anyone has a way to explain it.
Cheers
Richard
prev parent reply other threads:[~2010-04-14 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 7:34 SVN bridge for multiple SVN modules Richard Dallaway
2010-04-14 6:08 ` Steven Michalske
2010-04-14 12:43 ` Richard Dallaway [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=v2ye3041f5c1004140543w11a16b48ye3095b266c0bc9b1@mail.gmail.com \
--to=dallaway@gmail.com \
--cc=git@vger.kernel.org \
--cc=smichalske@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).