git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Enforcing clone/fetch to use references.

From
David Brown <davidb@codeaurora.org>
Date
Sep 21, 2010, 20:44 UTC
Message-ID
<20100921204456.GA24357@huya.qualcomm.com>
[resending with corrected subject]

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.

Is there a way to do this? I've tried various ways of using alternates to keep the blobs out of the repository I want to export, but the daemon just follows the alternates. If I remove the alternates, I then seem to have a broken repository. Most things I try, at least carry objects for all of the files in the HEAD tree, which most of the time is a large portion of the data.

If there isn't a way of doing this currently, is this something that others would find useful?

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: Jeff King
Message 1 of 4 in “Enforcing clone/fetch to use references.”
  1. David BrownSep 21, 2010
  2. Jeff KingSep 21, 2010
  3. David BrownSep 21, 2010
  4. Arun RaghavanSep 23, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.