From: Marc Strapetz <marc.strapetz@syntevo.com>
To: Jacob Keller <jacob.keller@gmail.com>, Jeff King <peff@peff.net>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
Git mailing list <git@vger.kernel.org>
Subject: Re: git submodule should honor "-c credential.helper" command line argument
Date: Sun, 7 Feb 2016 14:48:07 +0100 [thread overview]
Message-ID: <56B74B17.4040304@syntevo.com> (raw)
In-Reply-To: <CA+P7+xr4gQFPsUiuqSzMsUJP6_W8FnXBwX1Xes=XjksuTs=+hQ@mail.gmail.com>
On 07.02.2016 05:41, Jacob Keller wrote:
> On Wed, Feb 3, 2016 at 3:44 PM, Jacob Keller <jacob.keller@gmail.com> wrote:
>> Ok so I am not sure we even really need to use "-c" option in
>> git-clone considering that we can just use the same flow we do for
>> setting core.worktree values. I'll propose a patch with you two Cc'ed,
>> which I think fixes the issue. There may actually be a set of
>> configuration we want to include though, and the main issue I see is
>> that it won't get updated correctly whenever the parent configuration
>> changes.
>>
>> Thanks,
>> Jake
>
> I tried adding the config as part of module_clone in
> submodule--helper.c but it didn't pass the test I added. I haven't had
> time to look at this in the last few days, but I am stuck as to why
> submodule--helper.c appeared to not use module_clone as I thought.
I've tried to just comment out clearing of environment variables in
git-sh-setup.sh, clear_local_git_env(). I've noticed that "-c
credentials-helper ..." is stored in $GIT_CONFIG_PARAMETERS and with
existing code is reset there. If not clearing the environment variables,
at least "git submodule init" is working properly. I didn't try with
other commands nor to run tests.
-Marc
next prev parent reply other threads:[~2016-02-07 13:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 17:13 git submodule should honor "-c credential.helper" command line argument Marc Strapetz
2016-02-03 4:25 ` Jeff King
2016-02-03 7:35 ` Jacob Keller
2016-02-03 8:08 ` Marc Strapetz
2016-02-03 23:44 ` Jacob Keller
2016-02-07 4:41 ` Jacob Keller
2016-02-07 13:48 ` Marc Strapetz [this message]
2016-02-08 3:44 ` Jacob Keller
2016-02-19 1:15 ` Jacob Keller
2016-02-19 4:30 ` Jeff King
2016-02-19 7:29 ` Jacob Keller
2016-02-19 7:46 ` Jeff King
2016-02-19 7:51 ` Jacob Keller
2016-02-19 17:33 ` Junio C Hamano
2016-02-19 19:34 ` Jacob Keller
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=56B74B17.4040304@syntevo.com \
--to=marc.strapetz@syntevo.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
--cc=peff@peff.net \
/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).