From: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
To: git@vger.kernel.org
Subject: Re: Most elegant way to reference to SVN from GIT?
Date: Sun, 18 Sep 2011 13:20:47 +0200 [thread overview]
Message-ID: <j54keg$ug9$1@dough.gmane.org> (raw)
In-Reply-To: <20110918034318.GC17977@sigill.intra.peff.net>
Jeff King wrote:
> You can pull their commits into git using git-svn, and then merge them.
Tried that, but maybe I did something wrong.
If I have a git-svn repo inside my git repo, then for some reason my own repo
doesn't known the git-svn repo. Means that I cannot push changes, that occured
in the SVN repo, to my GIT server.
So I'm still searching for an elegant way to get SVN into my GIT repo. As
submodules make it more difficult to clone the project, I think it would be nice
to be just able to fetch the stuff from SVN "commit by commit" and then have
them as git commits in my own tree. So far I wasn't able to get this done...
Yours
Manuel
next prev parent reply other threads:[~2011-09-18 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 23:51 Most elegant way to reference to SVN from GIT? Manuel Reimer
2011-09-18 3:43 ` Jeff King
2011-09-18 11:20 ` Manuel Reimer [this message]
2011-09-18 18:47 ` Jakub Narebski
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='j54keg$ug9$1@dough.gmane.org' \
--to=manuel.spam@nurfuerspam.de \
--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).