Re: Enforcing clone/fetch to use references.

From: David Brown <davidb@codeaurora.org>
Date: Sep 21, 2010, 22:12 UTC
Message-ID: <20100921221229.GA29680@huya.qualcomm.com>
In-Reply-To: <20100921213135.GB1255@sigill.intra.peff.net>

On Tue, Sep 21, 2010 at 05:31:35PM -0400, Jeff King wrote:

Show 20 quoted lines

> On Tue, Sep 21, 2010 at 01:44:56PM -0700, David Brown wrote:
> 
> > Suppose I want to publish some changes to a tree.  I have a server
> > available where I can run a git daemon, but for one reason or another
> > I want to force people to use the another git repo as a reference.
> > The reason could be one of bandwidth, or someone who isn't comfortable
> > making all of the other source available.  Ideally, someone who
> > already has the other git repo cloned, and just adds mine as a remote
> > wouldn't notice the difference.
> 
> I think the gentoo people were talking about doing something like this.
> They wanted you to use some faster and/or restartable protocol to clone
> initially, and so they wanted to reject initial clones. I'm not sure if
> they are doing that, and how (from the thread below, I suspect they run
> a patched git).
> 
> The simplest thing would be a pre-upload-pack hook. There was some
> discussion of that in this thread:
> 
>   http://article.gmane.org/gmane.comp.version-control.git/137007

Arun, did you ever get a chance to rework the upload-pack hooks to work only from git daemon? If not, I'd like to take a look into implementing this.

Thanks, David

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.