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

Re: Linking two remote repositories

From
Jens Lehmann <jens.lehmann@web.de>
Date
Mar 12, 2010, 16:10 UTC
Message-ID
<4B9A675F.6050309@web.de>
In-Reply-To
<loom.20100312T145901-192@post.gmane.org>
Am 12.03.2010 15:09, schrieb Pavel:
Show 12 quoted lines
> Hi All,
> I'm just investigating of using git for following:
> We have two development teams in far direction from each other and very slow
> network connection between them. Currently they are using one Subversion
> repository on one side, but committing from other side is very-very slow. 
> 
> The idea is to setup two git repositories in two locations and developers will
> commit in there local repository. But what I can't figure out it's how to
> connect those repositories between each other, I do not want to have two
> "special" people to push between remote repositories. 
> Is there any ideas how to connect two repositories and have actual code versions
> on both of them ?

Having a similar setup at my dayjob, I think it should be sufficient to have only one git server (maybe at the location where your svn-server is now). As git keeps a local copy of the whole repo operations like commit, diff and merge are fast and independent of network speed. Only clone, fetch and push go over the slow network connection, but for us this is fast enough (and a lot faster than our old RCS based VCS, which was basically unusable for this scenario).

Previous: Pavel
Message 2 of 2 in “Linking two remote repositories”
  1. PavelMar 12, 2010
  2. Jens LehmannMar 12, 2010

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.