From: Josh Triplett <josh@joshtriplett.org>
To: Richard <richard.maw@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Adding more namespace support to git
Date: Sun, 21 Aug 2016 07:07:10 -0700 [thread overview]
Message-ID: <20160821140710.qpbm37nhhvbkmxgz@x> (raw)
In-Reply-To: <CAB2VqoZdj1rhdt-4gUhXTAMQjJTOqCuwXiO6yfB2Fzyy_qSWHg@mail.gmail.com>
On Sun, Aug 21, 2016 at 12:30:16PM +0100, Richard wrote:
> On 21 August 2016 at 03:05, Josh Triplett <josh@joshtriplett.org> wrote:
> > Unfortunately, I think at this point, GIT_NAMESPACE has to exclusively
> > refer to the namespace for the remote end, to avoid breakage. Which
> > means any automatic pervasive support for namespaces on the local side
> > would need to use a different mechanism. (In addition to applying to
> > ref enumeration, this would also need to apply to the local end of
> > refspecs.) And this new mechanism would need to not affect the remote
> > end, to allow remapping the local end while accessing an un-namespaced
> > (or differently namespaced) remote.
>
> The problem for hooks is that it is implicitly inherited,
> so it could work if upload-pack receive-pack and http-backend work
> with GIT_NAMESPACE set,
> but everything else that wants to use a namespace has to set
> --namespace on the command-line.
I'd like to see it work more automatically than that. Perhaps a
separate environment variable to set the client-side namespace?
next prev parent reply other threads:[~2016-08-21 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-20 19:07 Adding more namespace support to git Richard
2016-08-21 2:05 ` Josh Triplett
2016-08-21 11:30 ` Richard
2016-08-21 14:07 ` Josh Triplett [this message]
[not found] ` <CAB2Vqoa+1QKD-7zjNUJBuu2qNowgY7n9fLM77zUdzf8aJi4XaQ@mail.gmail.com>
2016-08-22 19:16 ` Josh Triplett
2016-08-22 19:36 ` Richard
2016-08-24 17:49 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160821140710.qpbm37nhhvbkmxgz@x \
--to=josh@joshtriplett.org \
--cc=git@vger.kernel.org \
--cc=richard.maw@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).