All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georg Lohrer <pacco@tropezien.de>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: How to use git-svnimport without trunk, tags and branches?
Date: Sun, 11 Mar 2007 17:57:13 +0100	[thread overview]
Message-ID: <45F434E9.7040003@tropezien.de> (raw)
In-Reply-To: <20070311143638.GA7822@diana.vm.bytemark.co.uk>

Hi Karl,

Karl Hasselström schrieb:
  > You could try something like this:
> 
>   trunk: svnrepos/projectA
>   tags: svnrepos/dummytags
>   branches: svnrepos/dummybranches
> 
> I haven't tested, but I think that kind of maneouver should work.

yes, that does the trick. I use:

$ cd ~/tmp/git-test
$ tar xvfj fooRepos.tar.bz2
$ mv fooRepos foorRepos.svnrepos
$ svn mkdir file:///home/georg/tmp/git-test/fooRepos.svnrepos/dummytags
$ svn mkdir file:///home/georg/tmp/git-test/foorRepos.svnrepos/dummybranches
$ mkdir fooRepos.git; cd fooRepos.git
$ git-svnimport -b dummybranches -t dummytags -T projectA 
file:///home/georg/tmp/git-test/fooRepos.svnrepos

Unfortunately there was a bunch of directories  instead of a single 
projectA-directory. Do I have to repeat the above mentioned sequence for 
every directory (projectA, projectB, ...) or is there a simple way of 
git-svnimport'ing into an existing git-repository?

Nevertheless, if that is not possible, I could extract with your way 
the desired directories separately and keep the histories intact.

Regards, Georg

  reply	other threads:[~2007-03-11 16:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-11 11:38 How to use git-svnimport without trunk, tags and branches? Georg Lohrer
2007-03-11 14:36 ` Karl Hasselström
2007-03-11 16:57   ` Georg Lohrer [this message]
2007-03-11 20:26     ` Karl Hasselström
2007-03-12 15:10       ` pacco

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=45F434E9.7040003@tropezien.de \
    --to=pacco@tropezien.de \
    --cc=git@vger.kernel.org \
    --cc=kha@treskal.com \
    /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.