From: David Brown <davidb@codeaurora.org>
To: Arun Raghavan <ford_prefect@gentoo.org>
Cc: git@vger.kernel.org
Subject: Re: Enforcing clone/fetch to use references.
Date: Tue, 21 Sep 2010 15:12:29 -0700 [thread overview]
Message-ID: <20100921221229.GA29680@huya.qualcomm.com> (raw)
In-Reply-To: <20100921213135.GB1255@sigill.intra.peff.net>
On Tue, Sep 21, 2010 at 05:31:35PM -0400, Jeff King wrote:
> 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.
next prev parent reply other threads:[~2010-09-21 22:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 20:44 Enforcing clone/fetch to use references David Brown
2010-09-21 21:31 ` Jeff King
2010-09-21 22:12 ` David Brown [this message]
2010-09-23 12:39 ` Arun Raghavan
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=20100921221229.GA29680@huya.qualcomm.com \
--to=davidb@codeaurora.org \
--cc=ford_prefect@gentoo.org \
--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;
as well as URLs for NNTP newsgroup(s).