Re: Why doesn't git-fetch obey -c "remote.origin.url" on the command-line?

[Jeff King <peff@peff.net>]

On Fri, Jun 13, 2014 at 09:37:07AM +0200, Ævar Arnfjörð Bjarmason wrote:

> On a git built from the master branch just now:
> 
>  $ ./git config remote.origin.url
> https://code.google.com/p/git-core/
> $ ./git -c remote.origin.url=git://git.sourceforge.jp/gitroot/git-core/git.git
> config remote.origin.url
> git://git.sourceforge.jp/gitroot/git-core/git.git
> $ GIT_TRACE=1 ./git -c
> remote.origin.url=git://git.sourceforge.jp/gitroot/git-core/git.git
> fetch 2>&1 | head -n 2
> trace: built-in: git 'fetch'
> trace: run_command: 'git-remote-https' 'origin'
> 'https://code.google.com/p/git-core/'
> 
> I'd expect this to try to fetch from the remote.origin.url I specified
> on the command-line, but for some reason fetch doesn't pick that up.
> Isn't this a bug?

I think this is an alternate version of the report in [1].

The short answer is: remote.*.url is a multi-valued config option, and
you can only append to (not override) such options with "git -c". Try
using insteadOf.

-Peff

[1] http://article.gmane.org/gmane.comp.version-control.git/250427