From: Heiko Voigt <hvoigt@hvoigt.net>
To: Christoph Bartoschek <bartoschek@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Migrating from SVN
Date: Thu, 25 Mar 2010 07:22:14 +0100 [thread overview]
Message-ID: <20100325062214.GA1829@book.hvoigt.net> (raw)
In-Reply-To: <aosj77-m7e.ln1@burns.bruehl.pontohonk.de>
On Mon, Mar 22, 2010 at 11:18:18AM +0100, Christoph Bartoschek wrote:
> Now we are merging both products into one such that the structure should be
>
> product/project_A
> project_B
> project_C
> project_D
> project_E
>
> I think this makes migration to Git easier as we can now work with only one
> Git repository. We also circumvent the usage of the unmature submodule
> support in Git.
>
> How can I now import our Subversion projects into the Git repository such
> that for each project the history is kept and ideally the whole history is
> linearized by the subversion revision numbers?
Import them all seperately into git (e.g. using git svn) and then have a
look at subtree merge
http://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html
to merge them all together. That way you will have seperate lines of
history for each project and one (or five) big merges on top.
AFAIK the revision number from svn is stored in the commit message if
you use git svn so to add the project name you might want to use git
filter-branch to add that name to each commit before merging the history
lines.
That way you will have all the history of the now seperate projects in
one git repository. Keep in mind that after doing that its not that easy
to make them seperate projects again.
Hope that helps.
cheers Heiko
next prev parent reply other threads:[~2010-03-25 6:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 10:18 Migrating from SVN Christoph Bartoschek
2010-03-25 6:22 ` Heiko Voigt [this message]
2010-03-26 11:15 ` Christoph Bartoschek
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=20100325062214.GA1829@book.hvoigt.net \
--to=hvoigt@hvoigt.net \
--cc=bartoschek@gmx.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).