From: "Alf Mikula" <amikula@gmail.com>
To: "Martin Langhoff" <martin.langhoff@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Migrating a git repository to subversion
Date: Fri, 16 May 2008 10:45:35 -0700 [thread overview]
Message-ID: <42dc968d0805161045g1b128360ha45e8bdf9ced6fe6@mail.gmail.com> (raw)
In-Reply-To: <46a038f90805152053n43add2cbj8383c475772c3681@mail.gmail.com>
> The git svn rebase trick described earlier does almost exactly what Alf wants.
You're absolutely right. With the rebase, I have my history (which so
far is linear) in the SVN repository, and I can continue using git
locally and pushing my commits back to Subversion. I also want to try
Björn's suggestions about merging SVN branches. While Subversion
fixed the most annoying problems in CVS, I think it got a lot of
branching, merging, and tagging wrong. Maybe using git to handle
merging will make a nice band-aid.
Anyway, thanks to all for the suggestions!
-Alf
next prev parent reply other threads:[~2008-05-16 17:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 23:08 Migrating a git repository to subversion Alf Mikula
2008-05-15 23:19 ` Avery Pennarun
2008-05-15 23:47 ` Björn Steinbrink
2008-05-16 3:01 ` Linus Torvalds
2008-05-16 3:53 ` Martin Langhoff
2008-05-16 17:45 ` Alf Mikula [this message]
2008-05-16 4:59 ` Imran M Yousuf
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=42dc968d0805161045g1b128360ha45e8bdf9ced6fe6@mail.gmail.com \
--to=amikula@gmail.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@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).