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

[PATCH v2 0/2] lifting upload-archive restrictions

From
Jeff King <peff@peff.net>
Date
Feb 28, 2014, 09:56 UTC
Message-ID
<20140228095619.GA11803@sigill.intra.peff.net>
In-Reply-To
<20140228090709.GB11709@sigill.intra.peff.net>
On Fri, Feb 28, 2014 at 04:07:09AM -0500, Jeff King wrote:
Show 9 quoted lines
> > As this does not affect local use of "git archive", "requested by
> > refnames" may need to be clarified further.  Perhaps "remote
> > archives can be requested only for published refnames" or something.
> 
> I was hoping to be vague. If we really want to get into specifics, we
> should probably document the current rules (refnames, and sub-trees of
> refnames). It might be a good thing to document that anyway, though. And
> by doing so, it would become obvious why one would want to set this
> option. I'll see what I can come up with.

Here's a series to handle this; I think the end result is much nicer. I ended up calling the option "uploadarchive.allowUnreachable". By moving it there instead of under "archive", it is more clear that this is about the _serving_ end of the remote connection, and the word "remote" becomes redundant.

  [1/2]: docs: clarify remote restrictions for git-upload-archive
  [2/2]: add uploadarchive.allowUnreachable option
-Peff
Previous: Jeff KingNext: Jeff King
Message 4 of 8 in “archive: add archive.restrictRemote option”
  1. archive: add archive.restrictRemote optionJeff King, Feb 27, 2014
  2. Junio C HamanoFeb 27, 2014
  3. Jeff KingFeb 28, 2014
  4. 0/2 lifting upload-archive restrictionsJeff King, Feb 28, 2014
  5. 1/2 docs: clarify remote restrictions for git-upload-archiveJeff King, Feb 28, 2014
  6. 2/2 add uploadarchive.allowUnreachable optionJeff King, Feb 28, 2014
  7. Junio C HamanoFeb 28, 2014
  8. Junio C HamanoFeb 28, 2014

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.