git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samir Faci <samir@esamir.com>
To: git@vger.kernel.org
Subject: svn repo a submodule?
Date: Wed, 5 May 2010 09:43:20 -0500	[thread overview]
Message-ID: <g2i9db93b0e1005050743q43d745ebod1aa13f98ab5a44c@mail.gmail.com> (raw)

I've been using git submodule to refer to external repos that I don't
maintain.  (which works great)

So far in order to use an svn repo as a submodule I end up doing a git
svn clone, and basically have a crontab job that pulls from svn and
pushes to git repo.  Then I end up using the git repo it creates as a
git submodule.

The workflow does work, though it is a bit tedious.   I was wondering
if there was any particular reason why having an svn repo as a
submodule isn't supported at this time.  Or if there was a better way
of accomplishing this that escapes me.


--
Samir Faci
*insert title*
fortune | cowsay -f /usr/share/cows/tux.cow

                 reply	other threads:[~2010-05-05 14:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=g2i9db93b0e1005050743q43d745ebod1aa13f98ab5a44c@mail.gmail.com \
    --to=samir@esamir.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).