From: Chris Down <chris@chrisdown.name>
To: Git <git@vger.kernel.org>
Subject: http.proxy seems to not be propagated on `submodule update`
Date: Wed, 10 Dec 2014 17:05:46 +0000 [thread overview]
Message-ID: <20141210170546.GA50294@chrisdown.name> (raw)
[-- Attachment #1: Type: text/plain, Size: 3709 bytes --]
Hello,
I'm trying to recursively update submodules in a repo on a server that
requires a proxy to access the internet.
I typically pass http.proxy with -c to tell git about the proxy, but
with `submodule update`, it seems the argument isn't propagated and thus
results in the process sitting doing nothing when it tries to connect.
Is this expected behaviour?
cdown@dev023:dotfiles:linux$ GIT_TRACE=2 git -c http.proxy=fwdproxy.any:8080 submodule update --init --recursive
trace: exec: 'git-submodule' 'update' '--init' '--recursive'
trace: run_command: 'git-submodule' 'update' '--init' '--recursive'
trace: built-in: git 'rev-parse' '--git-dir'
trace: built-in: git 'rev-parse' '--show-cdup'
trace: built-in: git 'rev-parse' '-q' '--git-dir'
trace: built-in: git 'rev-parse' '--sq-quote' '--init'
trace: built-in: git 'rev-parse' '--sq-quote' '--recursive'
trace: built-in: git 'ls-files' '--error-unmatch' '--stage' '--'
trace: built-in: git 'config' '-f' '.gitmodules' '--get-regexp' '^submodule\..*\.path$'
trace: built-in: git 'config' 'submodule..vim/bundle/auto-save.url'
trace: built-in: git 'config' '-f' '.gitmodules' 'submodule..vim/bundle/auto-save.update'
trace: built-in: git 'config' '-f' '.gitmodules' '--get-regexp' '^submodule\..*\.path$'
trace: built-in: git 'config' 'submodule..vim/bundle/ctrlp.url'
trace: built-in: git 'config' '-f' '.gitmodules' 'submodule..vim/bundle/ctrlp.update'
trace: built-in: git 'config' '-f' '.gitmodules' '--get-regexp' '^submodule\..*\.path$'
trace: built-in: git 'config' 'submodule..vim/bundle/easymotion.url'
trace: built-in: git 'config' '-f' '.gitmodules' 'submodule..vim/bundle/easymotion.update'
trace: built-in: git 'config' '-f' '.gitmodules' '--get-regexp' '^submodule\..*\.path$'
trace: built-in: git 'config' 'submodule..vim/bundle/fugitive.url'
trace: built-in: git 'config' '-f' '.gitmodules' 'submodule..vim/bundle/fugitive.update'
trace: built-in: git 'config' '-f' '.gitmodules' '--get-regexp' '^submodule\..*\.path$'
trace: built-in: git 'config' 'submodule..vim/bundle/markdown.url'
trace: built-in: git 'config' '-f' '.gitmodules' 'submodule..vim/bundle/markdown.update'
trace: built-in: git 'config' '-f' '.gitmodules' '--get-regexp' '^submodule\..*\.path$'
trace: built-in: git 'config' 'submodule..vim/bundle/pathogen.url'
trace: built-in: git 'config' '-f' '.gitmodules' 'submodule..vim/bundle/pathogen.update'
trace: built-in: git 'config' '-f' '.gitmodules' '--get-regexp' '^submodule\..*\.path$'
trace: built-in: git 'config' 'submodule..vim/bundle/supertab.url'
trace: built-in: git 'config' '-f' '.gitmodules' 'submodule..vim/bundle/supertab.update'
trace: built-in: git 'ls-files' '--error-unmatch' '--stage' '--'
trace: built-in: git 'config' '-f' '.gitmodules' '--get-regexp' '^submodule\..*\.path$'
trace: built-in: git 'config' 'submodule..vim/bundle/auto-save.url'
trace: built-in: git 'config' 'submodule..vim/bundle/auto-save.update'
trace: built-in: git 'rev-parse' '--git-dir'
trace: built-in: git 'rev-parse' '--show-toplevel'
trace: built-in: git 'rev-parse' '--show-toplevel'
trace: built-in: git 'rev-parse' '--local-env-vars'
trace: built-in: git 'config' 'core.worktree' '../../../../../.vim/bundle/auto-save'
trace: built-in: git 'rev-parse' '--local-env-vars'
trace: built-in: git 'fetch'
trace: run_command: 'git-remote-https' 'origin' 'https://github.com/907th/vim-auto-save.git'
^C
cdown@dev023:dotfiles:linux$ git --version
git version 1.8.1
Thanks,
Chris
[-- Attachment #2: Type: application/pgp-signature, Size: 971 bytes --]
reply other threads:[~2014-12-10 17:05 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=20141210170546.GA50294@chrisdown.name \
--to=chris@chrisdown.name \
--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).