From: "Jörg Sommer" <joerg@alea.gnuu.de>
To: git list <git@vger.kernel.org>
Subject: Re: Question about git-svn import
Date: Tue, 18 Dec 2007 16:31:59 +0100 [thread overview]
Message-ID: <20071218153159.GA12549@alea.gnuu.de> (raw)
In-Reply-To: <4767724A.9040207@obry.net>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
Hello Pascal,
Pascal Obry schrieb am Tue 18. Dec, 08:10 (+0100):
> Steven Walter a écrit :
> > Not sure if this is the best way, but I would recommend cloning into two
> > repositories, then combining them.
>
> I feared that :)
It's not as complicated as you might think.
> > So you already have the newer
> > changes with the standard layout. You would now:
> >
> > $ git svn init <repo>
> >
> > And only fetch the revisions before the layout change. You could then
> > combine the two repositories using .git/info/grafts and
> > git-rewrite-branch.
>
> Hum, looks like something not easy to do (at least for a Git beginner
> like me) ! Any documentation on this ? Would you mind showing this on
> the example script I sent ?
I had the same problem. We changed the structure of our SVN repository
from /trunk/pkg to /pkg/trunk and git-svn couldn't deal with this.
I used the script posted in
http://lists.alioth.debian.org/pipermail/pkg-jed-devel/2007-December/001719.html
to do the switch.
Some suggestions:
1. Import both parts into one git repo into their own branches. (use
--prefix)
2. Use gitk to insprect the history to find bad commits, e.g. empty
commits or things git-svn imported wrong.
3. Use git-filter-branch with the --parent-filter to join the branches.
HTH, Jörg.
--
Die am Lautesten reden, haben stets am wenigsten zu sagen.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-12-18 22:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 17:18 Question about git-svn import Pascal Obry
2007-12-18 3:48 ` Steven Walter
2007-12-18 7:10 ` Pascal Obry
2007-12-18 15:31 ` Jörg Sommer [this message]
2007-12-19 11:29 ` Pascal Obry
2007-12-20 16:30 ` Pascal Obry
2007-12-20 16:52 ` Jörg Sommer
2007-12-21 13:11 ` 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=20071218153159.GA12549@alea.gnuu.de \
--to=joerg@alea.gnuu.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).