Re: submodule update and core.askpass

2013-11-22 Thread Dmitry Neverov
BTW, a workaround is to pass a path to askpass script in the GIT_ASKPASS environment variable. Jens Lehmann writes: > Am 16.11.2013 22:42, schrieb Thomas Rast: >> Dmitry Neverov writes: >> >>> git -c core.askpass=pass.sh clone main-repo >>> cd main-repo >>> git submodule init >>> git submodule

Re: submodule update and core.askpass

2013-11-16 Thread Jens Lehmann
Am 16.11.2013 22:42, schrieb Thomas Rast: > Dmitry Neverov writes: > >> 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

Re: submodule update and core.askpass

2013-11-16 Thread Thomas Rast
+cc Daniel and Jens Dmitry Neverov writes: > 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

submodule update and core.askpass

2013-11-16 Thread Dmitry Neverov
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