From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Cc: "Jens Lehmann" <Jens.Lehmann@web.de>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH] environment.c: add GIT_NAMESPACE to local_repo_env
Date: Tue, 21 Oct 2014 07:27:33 +0700 [thread overview]
Message-ID: <1413851253-22642-1-git-send-email-pclouds@gmail.com> (raw)
This environment variable is added in a1bea2c (ref namespaces:
infrastructure - 2011-07-05). This is clearly repo specific setting
and should not be propagated to subprograms.
In practice, this is not a problem because GIT_NAMESPACE seems
designed for use on the server side and while submodule traversal
stuff happens on the client side.
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
---
.. looks like the right thing to do..
environment.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/environment.c b/environment.c
index 565f652..16628d3 100644
--- a/environment.c
+++ b/environment.c
@@ -100,6 +100,7 @@ const char * const local_repo_env[] = {
NO_REPLACE_OBJECTS_ENVIRONMENT,
GIT_PREFIX_ENVIRONMENT,
GIT_SHALLOW_FILE_ENVIRONMENT,
+ GIT_NAMESPACE_ENVIRONMENT,
NULL
};
--
2.0.2.841.g8f98430
reply other threads:[~2014-10-21 0:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1413851253-22642-1-git-send-email-pclouds@gmail.com \
--to=pclouds@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
/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).