From: Johannes Sixt <j.sixt@viscovery.net>
To: Benoit Sigoure <tsuna@lrde.epita.fr>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Importing merges when converting repos from SVN to Git (fusing grafts in the Git history)
Date: Tue, 08 Jan 2008 16:13:21 +0100 [thread overview]
Message-ID: <47839311.2010606@viscovery.net> (raw)
In-Reply-To: <744EF0AD-4773-4A35-B772-94621E9ADA10@lrde.epita.fr>
Benoit Sigoure schrieb:
> I'm going to import the repositories with `git-svn' and then I'd like to
> rewrite the entire history to take these merges in account in the Git
> repo, if possible. This will probably help us merging the (former) SVN
> branches in our new Git repo. I know I can simulate a merge with a
> graft and I think it will be fairly easy to write a small script that
> parses the log and generates the corresponding graft file. Now the
> question is: how to make these grafts part of the *real* history so that
> we don't have to depend on the graft file anymore?
>
> I know this issue has already been raised on the ML (the "how to include
> grafts are real merges in the history" thing) but I couldn't find the
> corresponding posts and can't remember the conclusion...
git-filter-branch --tag-name-filter=cat --all
should do it. It rewrites nothing but the parenthood, so you will find
that the rewritten history shares everything with the original history up
to the first merge(s).
You better run this on a "cp -al" copy of the original converted
repository because it *overwrites* the tags.
-- Hannes
next prev parent reply other threads:[~2008-01-08 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 14:48 Importing merges when converting repos from SVN to Git (fusing grafts in the Git history) Benoit Sigoure
2008-01-08 15:13 ` Johannes Sixt [this message]
2008-01-21 18:36 ` Importing merges when converting repos from SVN to Git Benoit Sigoure
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=47839311.2010606@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=tsuna@lrde.epita.fr \
/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).