From: Dmitry Neverov <dmitry.neverov@jetbrains.com>
To: git@vger.kernel.org
Subject: submodule update and core.askpass
Date: Sun, 17 Nov 2013 01:24:30 +0400 [thread overview]
Message-ID: <m28uwoxcoh.fsf@nds-macbook-air.labs.intellij.net> (raw)
Hi,
it seems like "git submodule update" command doesn't respect the
core.askpass option specified in a command line. I have a repository
with a submodule, I serve it over http which requires an authorization
and both main repository and submodule require the same credentials. I
run the following commands (pass.sh is a script which prints a password
to stdout):
git -c core.askpass=pass.sh clone main-repo
cd main-repo
git submodule init
git submodule sync
git -c core.askpass=pass.sh submodule update
The last command asks for a password interactively.
I've run bisect, it seems like it started failing from commit
be8779f7ac9a3be9aa783df008d59082f4054f67. I've checked: submodule update
works fine in 1.8.5.rc2 with removed call to clear_local_git_env.
Is there any way to make git submodule update respect core.askpass
option, so one can use it in scripts?
--
Dmitry Neverov
next reply other threads:[~2013-11-16 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 21:24 Dmitry Neverov [this message]
2013-11-16 21:42 ` submodule update and core.askpass Thomas Rast
2013-11-16 22:39 ` Jens Lehmann
2013-11-22 12:33 ` Dmitry Neverov
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=m28uwoxcoh.fsf@nds-macbook-air.labs.intellij.net \
--to=dmitry.neverov@jetbrains.com \
--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).