From: Andreas Ericsson <ae@op5.se>
To: Rick Moynihan <rick@calicojack.co.uk>
Cc: git@vger.kernel.org
Subject: Re: managing git submodules with git-svn
Date: Wed, 20 Aug 2008 14:49:04 +0200 [thread overview]
Message-ID: <48AC12C0.1090303@op5.se> (raw)
In-Reply-To: <48ABE568.80106@calicojack.co.uk>
Rick Moynihan wrote:
> Hi all,
>
> We are currently using a mixture of git and svn to manage a project with
> an array of subprojects. We use git primarily for its excellent
> branching and merging support, and as a means of more effectively
> managing commits etc... We're not yet ready to make the leap entirely
> to git and find subversion still has a role, primarily due to some 3rd
> party upstream (e.g. Apache) projects using svn. SVN is also better
> supported by some of our tools/systems.
>
> Our project is made up of a number of subprojects, and I'd like to use
> git submodules to easily track and lock changes in component versions.
> git submodules appear to do exactly this, versioning the meta-repo with
> each subproject locked at a specific commit/SHA-1.
>
> My question is; is there anyway to easily do this but have git use
> git-svn manage the submodule? I think this makes sense and suspect it
> would be possible to do, though it looks like it's currently not a
> feature. Is this a feature anyone else would find useful?
>
Off the top of my head, just point your submodule to the incremental
git-svn import of the upstream repository and you're good to go.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
prev parent reply other threads:[~2008-08-20 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 9:35 managing git submodules with git-svn Rick Moynihan
2008-08-20 12:49 ` Andreas Ericsson [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=48AC12C0.1090303@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=rick@calicojack.co.uk \
/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).