From: Richard Dallaway <dallaway@gmail.com>
To: git@vger.kernel.org
Subject: SVN bridge for multiple SVN modules
Date: Tue, 13 Apr 2010 08:34:14 +0100 [thread overview]
Message-ID: <m2ue3041f5c1004130034h51eb196dke0ebb8b3634e7302@mail.gmail.com> (raw)
Hello
We've run into something we'd like to do with "git svn clone" that
looks like it should work, but doesn't appear to.
The task: we have an SVN repository with 38 modules in it (each with
their own branches, tags, and trunk) and we'd like to pull just two of
the modules into a single git repository -- but maintain the ability
to perform git svn rebase/fetch/dcommit as the SVN repository is
remaining active for some developers.
It looks like we should be able to point at the parent of the SVN
modules and use --ignore-paths=/a long regexp/ to do the job, but
we've not managed to get it to work yet and we're now wondering if
we're missing a few concepts in the git/svn bridging concepts. Or
maybe we've just not got the syntax right yet.
There's a related question we spotted on stackoverflow that indicates
this isn't possible:
http://stackoverflow.com/questions/898568/multiple-svn-projects-into-one-git-repository
If that is the case (can anyone confirm?), is there a way we can do
this by pulling each SVN module into a separate intermediate git
repository, then doing "something" to push on to our target single
repository.... a "something" that would still enable us to git svn
fetch and git svn dcommit back to the SVN repo?
Suggestions, clues, explanations all very welcome.
Regards
Richard
next reply other threads:[~2010-04-13 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 7:34 Richard Dallaway [this message]
2010-04-14 6:08 ` SVN bridge for multiple SVN modules Steven Michalske
2010-04-14 12:43 ` Richard Dallaway
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=m2ue3041f5c1004130034h51eb196dke0ebb8b3634e7302@mail.gmail.com \
--to=dallaway@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).