Re: [RFC PATCH] Introduce git-hive

From: Luke Kenneth Casson Leighton <luke.leighton@gmail.com>
Date: Aug 31, 2010, 16:47 UTC
Message-ID: <AANLkTikrQhzyPckN2t3+FzaJFzYboDRVfW3bPPZOGpJQ@mail.gmail.com>
In-Reply-To: <20100831155159.GD16034@foucault.redhat.com>

On Tue, Aug 31, 2010 at 4:52 PM, Casey Dahlin <cdahlin@redhat.com> wrote:

Show 7 quoted lines

> Bittorrent has the luxury of being able to proxy for the poor firewall-bound
> users since as long as there's one peer exposed to the internet you can have
> any two other peers connect to him and give him the data they want to exchange,
> to the benefit of all 3. Git won't work that way because not everyone in the
> swarm wants all chunks of data, so if you found a proxy node, you might have to
> make him carry data (possibly lots of data) that he has no personal interest
> in.

 ah, no you don't.

 but - think about it: even if they don't, if they don't want the set
of commits that get you up to a particular HEAD or other tag or
branch, what the hell are they doing?? :)  from what i can gather, git
simply doesn't operate in a way where you can "pick and choose" which
commits you are and are not going to keep around, in order to
reconstruct the repository.

 i hope that's right, because i'm counting on it.  i.e i'm counting on
the following being true:

 "all copies of all git repositories have exactly the same objects
such that git pack-object on the exact same ref and the exact same
object ref will return exactly the same information".

 if anyone knows a reason why that is NOT the case, please could you tell me!

l.