git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Eivind LM" <eivliste@online.no>
To: "Jonathan del Strother" <maillist@steelskies.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Split a subversion repo into several git repos
Date: Fri, 12 Oct 2007 16:47:12 +0200	[thread overview]
Message-ID: <op.tz290yyfjwclfx@ichi> (raw)
In-Reply-To: <1B9700E6-5DFB-443D-9465-30E0DCAD0619@steelskies.com>

On Fri, 12 Oct 2007 16:23:44 +0200, Jonathan del Strother  
<maillist@steelskies.com> wrote:
[...]
>>
>>  $ git-svn init -b eivindlm/branches \
>>                 -t eivindlm/tags \
>>                 -T eivindlm/trunk/src/probesimulator \
>>                 file:///svn-repo/
>> , which prints the happy message:
>>  Initialized empty Git repository in .git/
>>
>> The next command is unfortunately not as happy:
>>  $ git fetch
>>  fatal: 'origin': unable to chdir or not a git archive
>>  fatal: The remote end hung up unexpectedly
>>  Cannot get the repository state from origin
>
>
> I believe you actually wanted "git-svn fetch" here

You are right, that solved the problem :)

So both methods work now, apparently giving the same result. Is there a  
difference between the fetch- versus the clone-approach? I am doing this  
as a once-and-for-all import, and would like to forget everything about  
the subversion repository afterwards.

Thanks,
Eivind

  reply	other threads:[~2007-10-12 14:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 12:51 Split a subversion repo into several git repos Eivind LM
2007-10-11 13:24 ` Patrick Doyle
2007-10-12 14:15   ` Eivind LM
2007-10-11 13:46 ` Jonathan del Strother
2007-10-11 14:02   ` Patrick Doyle
2007-10-11 14:50     ` Karl Hasselström
2007-10-11 21:40   ` Sam Vilain
2007-10-12 14:14     ` Eivind LM
2007-10-12 14:23       ` Jonathan del Strother
2007-10-12 14:47         ` Eivind LM [this message]
2007-10-12 20:27       ` 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=op.tz290yyfjwclfx@ichi \
    --to=eivliste@online.no \
    --cc=git@vger.kernel.org \
    --cc=maillist@steelskies.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 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).