git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sitaram Chamarty <sitaramc@gmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Cc: milki <milki@rescomp.berkeley.edu>
Subject: optimising a push by fetching objects from nearby repos
Date: Sat, 10 May 2014 19:09:37 +0530	[thread overview]
Message-ID: <536E2C19.3000202@gmail.com> (raw)

Hi,

Is there a trick to optimising a push by telling the receiver to pick up
missing objects from some other repo on its own server, to cut down even
more on network traffic?

So, hypothetically,

     git push user@host:repo1 --look-for-objects-in=repo2

I'm aware of the alternates mechanism, but that makes the dependency on
the other repo sort-of permanent.  I'm looking for a temporary
dependence, just for the duration of the push.  Naturally, the objects
should be brought into the target repo for that to happen, except that
this would be doing more from disk and less from the network.

My gut says this isn't possible, and I've searched enough to almost be
sure, but before I give up, I wanted to ask.

thanks
sitaram

Milki: I'm sure you won't mind the cc, since you know the context :-)

             reply	other threads:[~2014-05-10 13:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-10 13:39 Sitaram Chamarty [this message]
2014-05-10 13:54 ` optimising a push by fetching objects from nearby repos Duy Nguyen
2014-05-10 17:23 ` brian m. carlson
2014-05-10 17:32   ` milki
2014-05-10 20:04     ` brian m. carlson
2014-05-10 21:02 ` Junio C Hamano
2014-05-11  1:04   ` Sitaram Chamarty
2014-05-11  1:34     ` Storm-Olsen, Marius
2014-05-11  2:10       ` Sitaram Chamarty
2014-05-11  3:11         ` Storm-Olsen, Marius
2014-05-11  5:21           ` Sitaram Chamarty
2014-05-11 18:04             ` Junio C Hamano
2014-05-12  1:50               ` Sitaram Chamarty

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=536E2C19.3000202@gmail.com \
    --to=sitaramc@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=milki@rescomp.berkeley.edu \
    /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;
as well as URLs for NNTP newsgroup(s).