All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Jarosch <thomas.jarosch@intra2net.com>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Michael J Gruber <git@drmicha.warpmail.net>, git@vger.kernel.org
Subject: Re: help needed: Splitting a git repository after subversion migration
Date: Wed, 10 Dec 2008 17:33:28 +0100	[thread overview]
Message-ID: <200812101733.36221.thomas.jarosch@intra2net.com> (raw)
In-Reply-To: <200812081834.26688.thomas.jarosch@intra2net.com>

On Monday, 8. December 2008 18:34:20 Thomas Jarosch wrote:
> 1. When I run "git rev-list --all --objects", I can see file names that
> look like "SVN-branchname/directory/filename". Is it normal that "git svn"
> creates a directory with the name of the branch and puts files below it?

Ok, this seems to be a PEBKAC: In the history of the subversion repository, 
f.e. I once copied the "branches" root folder to tags/xyz. One revision later 
I noticed this and retagged the correct branch. git-svn imports all branches
from the first tag, which is the correct thing to do :o)

Now I'll manually check the history of the tags/ and branches/ folder
for more funny tags and write down the revision. If I understood
the git-svn man page correctly, I should be able to specifiy
revision ranges it's going to import. I'll try to skip the broken tags.

Cheers,
Thomas

  reply	other threads:[~2008-12-10 16:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-07 17:41 help needed: Splitting a git repository after subversion migration Thomas Jarosch
2008-12-08 13:30 ` Michael J Gruber
2008-12-08 14:24   ` Björn Steinbrink
2008-12-08 17:34     ` Thomas Jarosch
2008-12-10 16:33       ` Thomas Jarosch [this message]
2008-12-11  8:10         ` Björn Steinbrink
2008-12-12 14:22           ` Thomas Jarosch
2008-12-12 14:49             ` Björn Steinbrink

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=200812101733.36221.thomas.jarosch@intra2net.com \
    --to=thomas.jarosch@intra2net.com \
    --cc=B.Steinbrink@gmx.de \
    --cc=git@drmicha.warpmail.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.