Re: Fwd: git clone does not respect command line options

On Sun, Feb 28, 2016 at 09:03:43AM +0530, Guilherme wrote: > What is the current situation if credential.helper is set twice in the same > config file. > > Either > [credential] > helper = first > helper = second > > or with > [credential] > helper = first > > [credenital] > helper =

Re: Fwd: git clone does not respect command line options

What is the current situation if credential.helper is set twice in the same config file. Either [credential] helper = first helper = second or with [credential] helper = first [credenital] helper = second Will both be used by git clone? How do i remove these from the command line? I

Re: Fwd: git clone does not respect command line options

Jeff King writes: > That's behaving as expected. Unfortunately, you cannot currently do what > you want easily; there is no way to "unset" a multi-valued config > variable (like credential.helper) with a later one. Git will ask both > configured helpers for the password, and will

Re: Fwd: git clone does not respect command line options

On Fri, Feb 26, 2016 at 03:23:58PM +0530, Guilherme wrote: > I did try -c credential.helper= and there was a second problem with that > because an unset credential.helper is not the same as an empty > credential.helper. An empty one printed an error because it tried to invoke > 'git-credential-'.

Re: Fwd: git clone does not respect command line options

On Fri, Feb 26, 2016 at 03:34:53PM +0700, Duy Nguyen wrote: > On Fri, Feb 26, 2016 at 3:24 PM, Jeff King wrote: > > As an alternative, it would be nice to have some config syntax for > > "clear the list". Maybe something like an empty string, which I think > > has no meaning for

Re: Fwd: git clone does not respect command line options

On Fri, Feb 26, 2016 at 3:24 PM, Jeff King wrote: > As an alternative, it would be nice to have some config syntax for > "clear the list". Maybe something like an empty string, which I think > has no meaning for the current multi-valued variables (at least not for > credential

Re: Fwd: git clone does not respect command line options

On Fri, Feb 26, 2016 at 12:15:46AM -0800, Jacob Keller wrote: > On Thu, Feb 25, 2016 at 11:59 PM, Jeff King wrote: > > Right. The "git-config" program doesn't know about the semantics of > > particular values (remember that in the early days, there were many > > porcelains which

Re: Fwd: git clone does not respect command line options

On Thu, Feb 25, 2016 at 11:59 PM, Jeff King wrote: > Right. The "git-config" program doesn't know about the semantics of > particular values (remember that in the early days, there were many > porcelains which built on top of git, and they could all store their own > config). Using

Re: Fwd: git clone does not respect command line options

On Fri, Feb 26, 2016 at 01:16:39PM +0530, Guilherme wrote: > Is there any documentation on which variables are muli-valued? There's no central registry. It's often mentioned in the documentation for a particular config option, but it looks like the credential.* config is not very clear about

Re: Fwd: git clone does not respect command line options

Thanks for the quick reply. Is there any documentation on which variables are muli-valued? git -c credential.helper="store --file=creds" config --get credential.helper only returns one value. How can i even know if there are multiple set. I mean someone might have just created an extra

Re: Fwd: git clone does not respect command line options

On Fri, Feb 26, 2016 at 12:17:49PM +0530, Guilherme wrote: > I'm trying to use git in an integration test and i'm having trouble > with configuration options. > > On windows developer machines we use wincred as our credenital helper > and thus have it set in ~/.gitconfig > > For the integration

Fwd: git clone does not respect command line options

Hi! I'm trying to use git in an integration test and i'm having trouble with configuration options. On windows developer machines we use wincred as our credenital helper and thus have it set in ~/.gitconfig For the integration test that is no use as it will make testing unauthorized logging in