Git development
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: git@vger.kernel.org
Subject: Client-side mirroring patches (v0)
Date: Wed, 25 Nov 2009 23:06:53 +1300	[thread overview]
Message-ID: <1259143617-26580-1-git-send-email-sam@vilain.net> (raw)

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

             reply	other threads:[~2009-11-25 10:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 10:06 Sam Vilain [this message]
2009-11-25 10:06 ` [PATCH 1/4] remote: allow mirroring to be specified, and document settings Sam Vilain
2009-11-25 10:06   ` [PATCH 2/4] fetch: try mirrors if selected Sam Vilain
2009-11-25 10:06     ` [PATCH 3/4] fetch --use-mirror: don't fetch with 'autotags' for actual fetch Sam Vilain
2009-11-25 10:06       ` [PATCH 4/4] fetch: cleanup refs with --use-mirror Sam Vilain
2009-11-26  1:20     ` [PATCH 2/4] fetch: try mirrors if selected Shawn O. Pearce
2009-11-26  0:58 ` Client-side mirroring patches (v0) Shawn O. Pearce
2010-01-01  0:05 ` Nanako Shiraishi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1259143617-26580-1-git-send-email-sam@vilain.net \
    --to=sam@vilain.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox