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

What is the best way to synchronize two *bare* repositories with each other?

From
LWLiebich, Wolfgang <wolfgang.liebich@siemens-enterprise.com>
Date
Nov 24, 2009, 21:19 UTC
Message-ID
<7FF082147E322048955113B6CB87A7C0081731C659@MCHP058A.global-ad.net>

Hi, Let's say I have two bare git repositories, bareA and bareB. I also have a third non-bare repo, lets call it workA. Coworkers also have their working repositories, they all synchronize back to repoA. My work repo can only synchronize directly with repoB. What is the best way to keep repoA and repoB synchronized to each other?

I solved that by defining (in the "config" file of repoB) a remote section for repoA, and I "fetch" from repoA by issuing "git remote update repoA", and I push back via "git push --all repoA".

This strange setup is necessary because of the security setup (my home development machine is not directly connected with the company intranet).

Is this a good way to solve that problem, or are there better methods?
Ciao,
- Wolfgang
Next: Alex Riesen
Message 1 of 2 in “What is the best way to synchronize two *bare* repositories with each other?”
  1. Liebich, WolfgangNov 24, 2009
  2. Alex RiesenNov 25, 2009

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.