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

Client-side mirroring patches (v0)

From
Sam Vilain <sam@vilain.net>
Date
Nov 25, 2009, 10:06 UTC
Message-ID
<1259143617-26580-1-git-send-email-sam@vilain.net>

Hey folks, this is the first stage of git mirroring - making the client support it in the face of a completely ignorant server. I intended to make the clean-up better, but I've been sitting on these for a couple of weeks so I thought it would be better to have them out there for people to have a squiz at.

The next stage would be for the mirror list to be communicated to clients over the network protocol and updated in the git config.

Also there is the matter of falling over to the next mirror should one not be reachable, but then we're getting into C weaknesses really. Should I plan to do exception recovery using 'longjmp' ? Also the process should be interruptible and provide a user menu. Again this seems like it would be very tedious and clumsy in C. How do people manage? Anyway, enjoy... Sam

Next: Sam Vilain
Message 1 of 8 in “Client-side mirroring patches (v0)”
  1. Sam VilainNov 25, 2009
  2. 1/4 remote: allow mirroring to be specified, and document settingsSam Vilain, Nov 25, 2009
  3. 2/4 fetch: try mirrors if selectedSam Vilain, Nov 25, 2009
  4. 3/4 fetch --use-mirror: don't fetch with 'autotags' for actual fetchSam Vilain, Nov 25, 2009
  5. 4/4 fetch: cleanup refs with --use-mirrorSam Vilain, Nov 25, 2009
  6. Shawn O. PearceNov 26, 2009
  7. Shawn O. PearceNov 26, 2009
  8. Nanako ShiraishiJan 1, 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.