From: Steven Walter <stevenrwalter@gmail.com>
To: Pascal Obry <pascal@obry.net>
Cc: git list <git@vger.kernel.org>
Subject: Re: Question about git-svn import
Date: Mon, 17 Dec 2007 22:48:36 -0500 [thread overview]
Message-ID: <20071218034836.GA27080@dervierte> (raw)
In-Reply-To: <4766AF65.5060706@obry.net>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
On Mon, Dec 17, 2007 at 06:18:29PM +0100, Pascal Obry wrote:
> You'll find a script into this message that reproduce what I'll describe
> below. Basically the Subversion repository add a given structure in the
> past then rearranged to use the "standard" structure. The former
> structure was:
>
> <root>
> |
> | - dir1
> | - dir2
>
> The new one is:
>
> <root>
> |
> |- trunk
> | | - dir1
> | | - dir2
> |- branches
> |- tags
>
> Now I want to import this project into Git (using git-svn) as the
> project won't leave Subversion for the moment. When doing:
>
> $ git svn clone -s <repo> <git-repo>
>
> In git-repo we get only the commits done inside <root>/trunk and not the
> commits done in the former repository.
>
> The question is what is the best way to deal with such a case with git-svn ?
Not sure if this is the best way, but I would recommend cloning into two
repositories, then combining them. 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.
--
-Steven Walter <stevenrwalter@gmail.com>
Freedom is the freedom to say that 2 + 2 = 4
B2F1 0ECC E605 7321 E818 7A65 FC81 9777 DC28 9E8F
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-12-18 3:49 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 [this message]
2007-12-18 7:10 ` Pascal Obry
2007-12-18 15:31 ` Jörg Sommer
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=20071218034836.GA27080@dervierte \
--to=stevenrwalter@gmail.com \
--cc=git@vger.kernel.org \
--cc=pascal@obry.net \
/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).