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

git remote repositories

From
DWDan Weber <dan@mirrorlynx.com>
Date
Apr 22, 2005, 23:38 UTC
Message-ID
<Pine.LNX.4.62.0504221929480.20133@mirrorlynx.com>
Hi,

It wasn't that long ago that the pasky git tree was relocated. This required a modification to the .git directory in a local pull. A dns system could be built to ensure the following:

A) quick easy lookup of archive locations B) handle changes of repository location C) add mirror support

So heres the plan... I do a lot of work in sip/voip field, and our approach to handling backup proxies and routers is to use a dns srv record.

Here's how it works for voip/sip.
_{protocol}._{transport}.{name}.hostname.org
A sample lookup:
dig SRV _sip._udp.proxy-dca.broadvoice.com

;; QUESTION SECTION: ;_sip._udp.proxy-dca.broadvoice.com. IN SRV

;; ANSWER SECTION: _sip._udp.proxy-dca.broadvoice.com. 86400 IN SRV 1 0 5060 proxy.mia.broadvoice.com. _sip._udp.proxy-dca.broadvoice.com. 86400 IN SRV 0 0 5060 proxy.dca.broadvoice.com.

Now of course we could null out some of those fields and swap sip for git and udp for rsync, then replace proxy.foo to rsync://host/path/to/git. Since we're using rsync, mirroring is simplified by just rsyncing the trees.

Dan
Next: Petr Baudis
Message 1 of 2 in “git remote repositories”
  1. Dan WeberApr 22, 2005
  2. Petr BaudisApr 23, 2005

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.