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

Best practices for maintaining a subversion mirror?

From
OCOliver Charles <oliver.g.charles@googlemail.com>
Date
Nov 24, 2008, 10:55 UTC
Message-ID
<5641883d0811240255i21aef729ld202bd5a3211dad9@mail.gmail.com>
Hi,

I just got myself a new server, and as I'm the major Git-using person at my work, I'd like to set a mirror of our Subversion repository up to hopefully convert a few more people. At the moment, I've done git svn clone http://svn..., and then git clone --bare to make a --bare version of this clone.

Now that I have this mirror, I have this entry in my crontab to update it hourly:

0 * * * * cd /.git && /usr/bin/git --git-dir=. svn fetch && /usr/bin/git update-ref refs/heads/master refs/remotes/git-svn

This seems to be working nicely as a readonly interface, but when I clone this repository (git clone git://foo/repo.git) - served via git-daemon - I can't seem to get svn rebase to work on it, which means I can't dcommit my changes back to Subversion.

Am I doing things generally the right way, or am I doing it completely wrong? :-) Any tips appreciated!

- Oliver Charles
Next: Peter Harris
Message 1 of 2 in “Best practices for maintaining a subversion mirror?”
  1. Oliver CharlesNov 24, 2008
  2. Peter HarrisNov 24, 2008

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.