git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* SVN bridge for multiple SVN modules
@ 2010-04-13  7:34 Richard Dallaway
  2010-04-14  6:08 ` Steven Michalske
  0 siblings, 1 reply; 3+ messages in thread
From: Richard Dallaway @ 2010-04-13  7:34 UTC (permalink / raw)
  To: git

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: SVN bridge for multiple SVN modules
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Steven Michalske @ 2010-04-14  6:08 UTC (permalink / raw)
  To: Richard Dallaway; +Cc: git

On Apr 13, 2010, at 12:34 AM, Richard Dallaway wrote:
> 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.
>
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?

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: SVN bridge for multiple SVN modules
  2010-04-14  6:08 ` Steven Michalske
@ 2010-04-14 12:43   ` Richard Dallaway
  0 siblings, 0 replies; 3+ messages in thread
From: Richard Dallaway @ 2010-04-14 12:43 UTC (permalink / raw)
  To: Steven Michalske; +Cc: git

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-04-14 12:43 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).