From: Steven Michalske <smichalske@gmail.com>
To: Richard Dallaway <dallaway@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: SVN bridge for multiple SVN modules
Date: Tue, 13 Apr 2010 23:08:05 -0700 [thread overview]
Message-ID: <236FD58B-CE33-4C06-A3AC-FD7DA7593EEB@gmail.com> (raw)
In-Reply-To: <m2ue3041f5c1004130034h51eb196dke0ebb8b3634e7302@mail.gmail.com>
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?
next prev parent reply other threads:[~2010-04-14 6:08 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 [this message]
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=236FD58B-CE33-4C06-A3AC-FD7DA7593EEB@gmail.com \
--to=smichalske@gmail.com \
--cc=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).