From: Michael J Gruber <git@drmicha.warpmail.net>
To: Tim Sally <tsally2@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Multiple SVN Repos Inside A Git Repo
Date: Wed, 03 Dec 2008 14:57:58 +0100 [thread overview]
Message-ID: <49369066.7030101@drmicha.warpmail.net> (raw)
In-Reply-To: <4753154c0812021222t2886f986id2b775f90d4ea7f@mail.gmail.com>
Tim Sally venit, vidit, dixit 02.12.2008 21:22:
> Using git-svn, it is possible to have different parts of a git repo
> correspond to a specific svn repo? From my understanding after reading
> the documentation, you need one git repository per svn. My example is
> that I'm trying to set up a git repo to version control everything
> from my classes, but each class has a separate svn repo. Also, the
> number of git repos I can create is limited, and I'd rather not
> clutter everything up with many separate git-svn repos.
>
> Example structure:
>
> class/
> .......... systems/
> .......... algorithms/
> .......... physics/
>
> class is one central git repository, and systems, algorithms, and
> physics contain data from three svn repositories. Ideally, you could
> commit/update to/from each svn repo individually, or all at once.
>
> Tim
You can have as many git svn configurations in a single git repo as you
want (see the "-R" argument to git svn). They will all correspond to
different remote branches. By checking out the branches (or a
corresponding tracking branch) you can switch between the branches, i.e.
between classes.
I don't think a layout as above is possible given your requirements that
- you (basically) want a single git repo and
- you want to be able to commit back.
They exclude using submodules resp. subtree merge.
Michael
prev parent reply other threads:[~2008-12-03 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 20:22 Multiple SVN Repos Inside A Git Repo Tim Sally
2008-12-03 13:57 ` Michael J Gruber [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=49369066.7030101@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=tsally2@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).