Re: [PATCH/RFC] receive-pack: allow for hiding refs outside the namespace

2015-10-31 Thread Lukas Fleischer
On Fri, 30 Oct 2015 at 22:46:19, Jeff King wrote: > On Fri, Oct 30, 2015 at 02:31:28PM -0700, Junio C Hamano wrote: > > > Lukas Fleischer writes: > > > > > 1. There does not seem to be a way to pass configuration parameters to > > >git-shell commands. Right now, the only

Re: [PATCH/RFC] receive-pack: allow for hiding refs outside the namespace

2015-10-30 Thread Junio C Hamano
Lukas Fleischer writes: > 1. There does not seem to be a way to pass configuration parameters to >git-shell commands. Right now, the only way to work around this seems >to write a wrapper script around git-shell that catches >git-receive-pack commands and executes

Re: [PATCH/RFC] receive-pack: allow for hiding refs outside the namespace

2015-10-30 Thread Jeff King
On Fri, Oct 30, 2015 at 02:31:28PM -0700, Junio C Hamano wrote: > Lukas Fleischer writes: > > > 1. There does not seem to be a way to pass configuration parameters to > >git-shell commands. Right now, the only way to work around this seems > >to write a wrapper

Re: [PATCH/RFC] receive-pack: allow for hiding refs outside the namespace

2015-10-28 Thread Jeff King
On Wed, Oct 28, 2015 at 08:00:45AM +0100, Lukas Fleischer wrote: > My original question remains: Do we want to continue supporting things > like transfer.hideRefs=.have (which currently magically hides all refs > outside the current namespace)? For 100% backwards compatibility, we > would have

Re: [PATCH/RFC] receive-pack: allow for hiding refs outside the namespace

2015-10-28 Thread Lukas Fleischer
On Tue, 27 Oct 2015 at 19:18:26, Junio C Hamano wrote: > [...] > When I asked 'Is transfer.hiderefs insufficient?', I wasn't > expecting it to be usable out of box. It was a suggestion to build > on top of it, instead of adding a parallel support for something > specific to namespaces. >

Re: [PATCH/RFC] receive-pack: allow for hiding refs outside the namespace

2015-10-28 Thread Junio C Hamano
Lukas Fleischer writes: > Another patch I have in my patch queue adds support for a whitelist mode > to hideRefs. There are several ways to implement that: > > 1. Make transfer.hideRefs='' hide all refs (it currently does not). The Hmph, that even sounds like a bug.

Re: [PATCH/RFC] receive-pack: allow for hiding refs outside the namespace

2015-10-27 Thread Junio C Hamano
Lukas Fleischer writes: > 2. transfer.hideRefs and receive.hideRefs do not seem to work with Git >namespaces in general. show_ref_cb() replaces each ref outside the >current namespace with ".have" before passing it to show_ref() which >in turn performs the

Re: [PATCH/RFC] receive-pack: allow for hiding refs outside the namespace

2015-10-27 Thread Lukas Fleischer
On Tue, 27 Oct 2015 at 06:59:11, Lukas Fleischer wrote: > [...] > On second thought, it might be possible to overwrite the value of > transfer.hiderefs using the -c command line option. If we combine that > with the negative patterns supported by hiderefs, we might get a > solution that is clean

[PATCH/RFC] receive-pack: allow for hiding refs outside the namespace

2015-10-26 Thread Lukas Fleischer
Right now, we always advertise all refs as ".have", even those outside the current namespace. This leads to problems when trying to push to a repository with a huge number of namespaces from a slow connection. Add a configuration option receive.advertiseAllRefs that can be used to determine

Re: [PATCH/RFC] receive-pack: allow for hiding refs outside the namespace

2015-10-26 Thread Junio C Hamano
Is there a reason why transfer.hiderefs is not sufficient? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html