From: Lukas Fleischer <lfleischer@lfos•de>
To: Jeff King <peff@peff•net>, "Junio C Hamano" <gitster@pobox•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH/RFC] receive-pack: allow for hiding refs outside the namespace
Date: Sat, 31 Oct 2015 10:03:11 +0100 [thread overview]
Message-ID: <20151031090311.26712.64475@typhoon.lan> (raw)
In-Reply-To: <20151030214618.GA11426@sigill.intra.peff.net>
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 <lfleischer@lfos•de> 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 something like
> > >
> > > git -c receive.hideRefs=[...] receive-pack [...]
> > >
> > > instead of forwarding those commands to git-shell.
> >
> > This part we have never discussed in the thread, I think. Why do
> > you need to override, instead of having these in the repository's
> > config files?
> >
> > Is it because a repository may host multiple pseudo repositories in
> > the form of "namespaces" but they must share the same config file,
> > and you would want to customize per "namespace"?
> >
Yes. As I said in the original thread, I want to set receive.hideRefs to
hide everything outside the current namespace, i.e. something equivalent
to
git -c receive.hideRefs='refs/' -c receive.hideRefs="!refs/namespaces/$foo" receive-pack /some/path
if receive.hideRefs would work with absolute (unstripped) namespaces.
> > For that we may want to enhance the [include] mechanism. Something
> > like
> >
> > [include "namespace=foo"]
> > path = /path/to/foo/specific/config.txt
> >
> > [include "namespace=bar"]
> > path = /path/to/bar/specific/config.txt
> >
> > Cc'ing Peff as we have discussed this kind of conditional inclusion
> > in the past...
>
That would work but it would still be very cumbersome. Imagine that
there is a single repository with 100000 pseudo repositories inside. You
really don't want to create a config file and a indirection in the main
configuration for each of these pseudo repositories, just to build a
configuration equivalent to the single line I described above.
> [...]
> I am slightly confused, though, where the namespace is set in such a
> git-shell example. I have no really used ref namespaces myself, but my
> understanding is that they have to come from the environment. You can
> similarly set config through the environment. I don't think we've ever
> publicized that, but it is how "git -c" works. E.g.:
>
> $ git -c alias.foo='!env' -c another.option=true foo | grep GIT_
> GIT_CONFIG_PARAMETERS='alias.foo='\!'env' 'another.option=true'
> [...]
Yes, the Git namespace is passed through the environment by setting
GIT_NAMESPACE and GIT_CONFIG_PARAMETERS is exactly what I was looking
for! Thanks!
next prev parent reply other threads:[~2015-10-31 9:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 8:09 [PATCH/RFC] receive-pack: allow for hiding refs outside the namespace Lukas Fleischer
2015-10-26 19:58 ` Junio C Hamano
[not found] ` <20151027053916.3030.8259@typhoon.lan>
[not found] ` <20151027055911.4877.94179@typhoon.lan>
2015-10-27 14:32 ` Lukas Fleischer
2015-10-27 18:18 ` Junio C Hamano
2015-10-28 7:00 ` Lukas Fleischer
2015-10-28 13:42 ` Jeff King
2015-10-28 15:48 ` Junio C Hamano
2015-10-30 21:31 ` Junio C Hamano
2015-10-30 21:46 ` Jeff King
2015-10-31 9:03 ` Lukas Fleischer [this message]
2015-10-28 15:42 ` [PATCH] Allow hideRefs to match " Lukas Fleischer
2015-10-28 16:21 ` Junio C Hamano
2015-10-31 8:49 ` Lukas Fleischer
2015-10-31 17:31 ` Junio C Hamano
2015-10-31 23:40 ` Lukas Fleischer
2015-11-01 11:27 ` Lukas Fleischer
2015-11-01 18:18 ` 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=20151031090311.26712.64475@typhoon.lan \
--to=lfleischer@lfos$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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