From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Scott J. Goldman" <scottjg@github.com>
Subject: [PATCH v2 0/2] lifting upload-archive restrictions
Date: Fri, 28 Feb 2014 04:56:19 -0500 [thread overview]
Message-ID: <20140228095619.GA11803@sigill.intra.peff.net> (raw)
In-Reply-To: <20140228090709.GB11709@sigill.intra.peff.net>
On Fri, Feb 28, 2014 at 04:07:09AM -0500, Jeff King wrote:
> > 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
next prev parent reply other threads:[~2014-02-28 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 4:05 [PATCH] archive: add archive.restrictRemote option Jeff King
2014-02-27 18:37 ` Junio C Hamano
2014-02-28 9:07 ` Jeff King
2014-02-28 9:56 ` Jeff King [this message]
2014-02-28 10:01 ` [PATCH v2 1/2] docs: clarify remote restrictions for git-upload-archive Jeff King
2014-02-28 10:04 ` [PATCH v2 2/2] add uploadarchive.allowUnreachable option Jeff King
2014-02-28 17:54 ` [PATCH v2 0/2] lifting upload-archive restrictions Junio C Hamano
2014-02-28 17:51 ` [PATCH] archive: add archive.restrictRemote option Junio C Hamano
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=20140228095619.GA11803@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=scottjg@github.com \
/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).