All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Obry <pascal@obry.net>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: git@vger.kernel.org
Subject: Re: git svn clone stops after r2 for svn://mlton.org/mlton/trunk
Date: Wed, 02 Feb 2011 21:19:11 +0100	[thread overview]
Message-ID: <4D49BC3F.5080902@obry.net> (raw)
In-Reply-To: <87aaijso0j.fsf@mid.deneb.enyo.de>


Florian,

> There's something strange going on there:
> 
> $ git svn clone svn://mlton.org/mlton/trunk mlton 
> Initialized empty Git repository in /home/fw/src/mlton/.git/
> r2 = 61f0dd5ba401ece2ff4668bc7454b7742c60fa99 (refs/remotes/git-svn)
> Checked out HEAD:
>   svn://mlton.org/mlton/trunk r2

This is probably because the first revision in trunk is r2 and there is
no r0 nor a r1. This repository has been converted from CVS (see r2). In
such a case you can convert properly using:

   $ git svn clone -s -r3:7500 svn://mlton.org/mlton mlton

r3 is the first actual revision, all see can be seen using:

   $ svn://mlton.org/mlton/trunk mlton

Note that I have used -s as this repository is using a standard svn layout.

Hope this helps.

Pascal.

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|    http://www.obry.net  -  http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B

      reply	other threads:[~2011-02-02 20:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-29 15:55 git svn clone stops after r2 for svn://mlton.org/mlton/trunk Florian Weimer
2011-02-02 20:19 ` Pascal Obry [this message]

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=4D49BC3F.5080902@obry.net \
    --to=pascal@obry.net \
    --cc=fw@deneb.enyo.de \
    --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.