git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-svn, tree moves, and --no-stop-on-copy

From
Yann Dirson <ydirson@altern.org>
Date
Mar 8, 2006, 22:41 UTC
Message-ID
<20060308224104.GC27397@nowhere.earth>
In-Reply-To
<20060308221524.GF12638@nowhere.earth>
On Wed, Mar 08, 2006 at 11:15:24PM +0100, Yann Dirson wrote:
> OTOH, this does work:
> 
>  svn co -r1 https://svn.sourceforge.net/svnroot/ufoai/trunk@1
Let's go further:
@@ -224,12 +227,14 @@ sub fetch {
        unless (-d $SVN_WC) {
                my @svn_co = ('svn','co',"-r$base->{revision}");
                push @svn_co,'--ignore-externals' unless $_no_ignore_ext;
-               sys(@svn_co, $SVN_URL, $SVN_WC);
+               sys(@svn_co, $SVN_URL . "\@$base->{revision}", $SVN_WC);
                chdir $SVN_WC or croak $!;


That allows git-svn not to fail at r1 (or at r3 when checking out
trunk/src only), and the 1st fetch runs OK.

The second fetch runs OK as well, but it shows the following somewhat
scary stuff before starting the import:

Checked out revision 166.
refs/remotes/git-newsvn
fatal: 'refs/remotes/git-newsvn': No such file or directory
r166 = 38a6ba0e3db486c65a611c54c53f838210ce7551


The results looks fine.  I don't know if it is expected to have the
master head stuck at remotes/git-oldsvn, though.

Thanks much for your help!
-- 
Yann Dirson    <ydirson@altern.org> |
Debian-related: <dirson@debian.org> |   Support Debian GNU/Linux:
                                    |  Freedom, Power, Stability, Gratis
     http://ydirson.free.fr/        | Check <http://www.debian.org/>
Previous: Yann DirsonNext: Eric Wong
Message 7 of 9 in “git-svn, tree moves, and --no-stop-on-copy”
  1. Yann DirsonMar 7, 2006
  2. Eric WongMar 8, 2006
  3. contrib/git-svn: fix UUID reading w/pre-1.2 svn; fetch argsEric Wong, Mar 8, 2006
  4. Junio C HamanoMar 9, 2006
  5. contrib/git-svn: fix svn compat and fetch argsEric Wong, Mar 9, 2006
  6. Yann DirsonMar 8, 2006
  7. Yann DirsonMar 8, 2006
  8. contrib/git-svn: remove the --no-stop-on-copy flagEric Wong, Mar 9, 2006
  9. Matthias UrlichsMar 8, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.