From: Penny Leach <penny@mjollnir.org>
To: git@vger.kernel.org
Subject: git-svn starting with an empty svn repository
Date: Tue, 24 Feb 2009 14:43:25 +0100 [thread overview]
Message-ID: <20090224134325.GA10719@mjollnir.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2581 bytes --]
Dear list,
This is maybe an abuse of what git-svn is designed to do, but nevertheless
I need to do it.
I'm working with a project (Moodle) that still uses CVS for its upstream
VCS. The friendly folk at Catalyst in NZ run a git import of this, that a
lot of the community uses as their (read only) upstream instead of CVS.
So far so good.
However, now for various political reasons, I must (at least) publish
changes to SVN. I'm going to be patch trading a lot between my work
branches, and Moodle's CVS directly and I don't want to lose the power that
git gives me while doing that. So I want to keep git as the tool I use for
development, that acts as a go-between for me between CVS and SVN.
So what I'd really like to do is something like this:
- clone from Catalyst's git mirror
- push that to SVN using git-svn
- keep working, committing patches to Moodle CVS, and pulling from Catalyst
regularly, while pushing both my local changes and new pulled upstream
patches, to SVN, using git-svn
The problem seems to be that I'm starting out with an *empty* SVN
repository. Almost all of the documentation I've found on this topic is
for going from an existing SVN repository to git.
Theoretically at least, the opposite direction should also be possible, but
I'm having a hard time figuring it out. I followed the steps outlined in
the comments here:
http://quirkygba.blogspot.com/2007/10/using-git-with-google-code-hosting.html
But I didn't have much luck, it seems as though the rebased trunk branch
doesn't share any ancestry with the original Catalyst sources, so regularly
updating is going to be hard (unless I create graft entries for each time I
do it I guess?).
Not to mention the fact that it's 8 years of history that takes a while to
import and after about 5 tries I didn't even manage to get git svn to
dcommit it and got impatient and cross and stopped trying.
So really I want to know is - is this even possible? Is using the above
steps along with the graft approach the best|only way to do it? How
brittle is this to maintain, if I even manage to get it imported?
Any ideas or advice?
For reference, the CVS/Git import can be cloned here:
http://git.catalyst.net.nz/git/moodle-r2.git but will take a long time to
come down.
Cheers for any help.
Penny
--
/* ---------------------------------------------------
Penny Leach | http://mjollnir.org | http://she.geek.nz
GPG: 8347 00FC B5BF 6CC0 0FC9 AB90 1875 120A A30E C22B
--------------------------------------------------- */
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-02-24 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 13:43 Penny Leach [this message]
2009-02-24 14:19 ` git-svn starting with an empty svn repository Pascal Obry
2009-02-24 15:03 ` Penny Leach
2009-02-24 15:36 ` Pascal Obry
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=20090224134325.GA10719@mjollnir.org \
--to=penny@mjollnir.org \
--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).