From: Jeff King <peff@peff.net>
To: Luciano Schillagi <luko.web@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: error
Date: Tue, 4 Oct 2016 13:27:47 -0400 [thread overview]
Message-ID: <20161004172747.ho53gxs3rcfucub7@sigill.intra.peff.net> (raw)
In-Reply-To: <CAK99BNA_2hwgkLUap_ThOG8drWkP6f74hdW=SNq_DpuNW=j2ew@mail.gmail.com> <C1F7B566-69F4-4A22-89EA-59B24677DF43@gmail.com>
[re-adding git@vger to the cc; please keep conversations on the list so
everybody can benefit from the answers]
On Tue, Oct 04, 2016 at 01:13:16PM -0300, Luciano Schillagi wrote:
> I ran the command
>
> Luko ~ $ git config --global --unset push.default
>
>
> and it gives me the following
>
> warning: push.default has multiple values
Ah, OK. "--unset-all" would do the trick, but it may only be one
instance that you want to get rid of...
> I can access my file .gitconfig
>
> I send attached...
> [...]
>
> [push]
> default = upstream
> default = aguas
Yep. Deleting the second line there will make your problem go away, and
presumably the first is a config setting you'd want to keep. That still
doesn't answer the question of how the "aguas" line got there, but I can
guess that at some point you might have set "push.default" instead of
"remote.pushdefault".
-Peff
next parent reply other threads:[~2016-10-04 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK99BNA_2hwgkLUap_ThOG8drWkP6f74hdW=SNq_DpuNW=j2ew@mail.gmail.com>
[not found] ` <C1F7B566-69F4-4A22-89EA-59B24677DF43@gmail.com>
2016-10-04 17:27 ` Jeff King [this message]
2016-09-22 23:02 error Luciano Schillagi
2016-09-23 4:46 ` error Jeff King
-- strict thread matches above, loose matches on Subject: below --
2013-07-10 1:30 Error Chanakya Vattikuti
2013-07-10 15:15 ` Error Konstantin Khomoutov
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161004172747.ho53gxs3rcfucub7@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=luko.web@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).