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

Re: [PATCH] Documentation/git-svn: Instructions for cloning a git-svn-created repository

From
EWEric Wong <normalperson@yhbt.net>
Date
Aug 10, 2007, 01:43 UTC
Message-ID
<20070810014312.GE9764@hand.yhbt.net>
In-Reply-To
<46BBADBB.6070502@midwinter.com>
Steven Grimm <koreth@midwinter.com> wrote:
Show 8 quoted lines
> Eric Wong wrote:
> >I personally believe using rsync to clone repositories created with
> >git-svn is the simplest and best method for now.
> 
> But then you don't get to use alternates -- one of the things I like 
> about the idea of doing a "git clone" of a git-svn repository is that 
> you could do "git clone -s" and get the full svn history with a tiny 
> .git directory.

If I'm working on multiple directories on the same machine, I have libflcow in my LD_PRELOAD and use cp -al (GNU-specific) to make hardlink images of my working directory. I've been using fl-cow with cp -al since long before I used git.

The new-ish git-new-workdir command could probably be a replacement for git-clone / flcow + cp -al / rsync in these situations as well.

-- 
Eric Wong
Previous: Steven Grimm
Message 5 of 5 in “Documentation/git-svn: Instructions for cloning a git-svn-created repository”
  1. Documentation/git-svn: Instructions for cloning a git-svn-created repositoryAdam Roben, Aug 6, 2007
  2. Junio C HamanoAug 6, 2007
  3. Eric WongAug 9, 2007
  4. Steven GrimmAug 10, 2007
  5. Eric WongAug 10, 2007

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.