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

Re: git-svn capabilities

From
Adam Roben <aroben@apple.com>
Date
Dec 9, 2007, 08:37 UTC
Message-ID
<475BA95F.7040403@apple.com>
In-Reply-To
<DB0B4F17-9E06-4C28-933E-FDEF9BAD6539@simplicidade.org>
Pedro Melo wrote:
Show 19 quoted lines
> Hi,
>
> I've been following along the gcc/git thread with interest and I've 
> used Harvey Harrison recipe
>
> http://article.gmane.org/gmane.comp.version-control.git/67253
>
> with success on several svn repos.
>
> One thing that I'm not sure yet if it is possible to do is this:
>
> can I have a single central git repo that tracks the svn repo, allow 
> several developers to use clone to copy that repo, and each one of 
> them (after proper manual configuration) uses dcommit to push back to 
> svn?
>
> All the recipes so far assume that each developer has to go through 
> the initial git-svn fetch and have a copy of the entire SVN repo, and 
> that seems wasteful to me.

The "Basic Examples" section of the git-svn man page describe how to do just that (though only for a single branch).

-Adam
Previous: Pedro MeloNext: Pedro Melo
Message 2 of 3 in “git-svn capabilities”
  1. Pedro MeloDec 9, 2007
  2. Adam RobenDec 9, 2007
  3. Pedro MeloDec 9, 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.