From: "David Neu" <david@davidneu.com>
To: "Miklos Vajna" <vmiklos@frugalware.org>
Cc: git@vger.kernel.org
Subject: Re: Converting from svn to git
Date: Sun, 10 Aug 2008 10:54:59 -0400 [thread overview]
Message-ID: <e0b44a890808100754l536bc4f3kfd953b52044f6e59@mail.gmail.com> (raw)
In-Reply-To: <20080810132409.GE18960@genesis.frugalware.org>
Thanks for the reply - this looks like what I'd need, but
I can't see how to keep the contents of the base dir and
lose the subdirs, e.g.
$ git-filter-branch --subdirectory-filter . HEAD
removes all subdirs and the contents of the base dir.
So, I figure I'd remove each subdir, using
$ git-filter-branch --tree-filter 'rm -rf subdir1/' HEAD
but this complains if subdir1 contains subdirectories, it
says: Namespace refs/original/ not empty
Many thanks!
Cheers,
David
On Sun, Aug 10, 2008 at 9:24 AM, Miklos Vajna <vmiklos@frugalware.org> wrote:
>
> On Sun, Aug 10, 2008 at 09:11:43AM -0400, David Neu <david@davidneu.com> wrote:
> > Is there a git-svn strategy similar to git-svnimport -P that would do the trick?
> > My git version 1.5.6.4 doesn't include git-svnimport, and I'm getting
> > the impression
> > it's be deprecated.
>
> Sure, it is. Though if you _really_ need it, it's still under
> /contrib/examples.
>
> Anyway, if you do a single conversion, then probably speed does not
> matter a lot; I would do a full import then use the subdirectory-filter
> of git filter-branch do drop everything outside the subdirectory.
next prev parent reply other threads:[~2008-08-10 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 13:11 Converting from svn to git David Neu
2008-08-10 13:24 ` Miklos Vajna
2008-08-10 14:54 ` David Neu [this message]
2008-08-10 15:32 ` Michael J Gruber
2008-08-10 15:48 ` David Neu
2008-08-11 17:46 ` David Neu
2008-08-15 13:58 ` Michael J Gruber
2008-08-17 9:11 ` Sam Vilain
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=e0b44a890808100754l536bc4f3kfd953b52044f6e59@mail.gmail.com \
--to=david@davidneu.com \
--cc=git@vger.kernel.org \
--cc=vmiklos@frugalware.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).