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

Re: git-svn and migration

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Dec 19, 2007, 20:23 UTC
Message-ID
<20071219202333.GD4390@genesis.frugalware.org>
In-Reply-To
<20071219175447.GB15898@dervierte>
On Wed, Dec 19, 2007 at 12:54:47PM -0500, Steven Walter <stevenrwalter@gmail.com> wrote:
Show 5 quoted lines
> Using a central git repo that is kept uptodate with svn is the approach
> I've used.  git-svn isn't especially keen on this mode of operation,
> however.  After every fetch, you have to reset refs/remotes/trunk to
> origin/master, which it turn puts .git/svn out of date (you can blow it
> away and run "git svn fetch" to regenerate it).

an other problem is that you probably want to have a bare repo while git-svn needs a working dir. a possible solution:

http://blogs.frugalware.org/vmiklos/2007/12/09/p320

(it works for me fine, but maybe there are problems with it so use with care :) )

- VMiklos
Previous: Steven WalterNext: Nigel Magnay
Message 3 of 5 in “git-svn and migration”
  1. Nigel MagnayDec 19, 2007
  2. Steven WalterDec 19, 2007
  3. Miklos VajnaDec 19, 2007
  4. Nigel MagnayDec 19, 2007
  5. Seth FalconDec 19, 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.