From: Felipe Contreras <felipe.contreras@gmail.com>
To: Caglar Akyuz <caglar.akyuz@sparsetechnology.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Ambiguous 'HEAD' issue.
Date: Sat, 27 Aug 2022 20:00:59 -0500 [thread overview]
Message-ID: <CAMP44s2iwWhpeBrzuRK5mB9ekpy4MRu5OEQ-BA4mvbUb1EJRqw@mail.gmail.com> (raw)
In-Reply-To: <AM0PR08MB4323160241D4341FB1B99CC2FD749@AM0PR08MB4323.eurprd08.prod.outlook.com>
On Sat, Aug 27, 2022 at 5:15 PM Caglar Akyuz
<caglar.akyuz@sparsetechnology.com> wrote:
> Recently I changed one of my repo's origin URL from gitlab to github. After this switch, I start getting:
>
> warning: refname 'HEAD' is ambiguous.
> * git show-ref | grep -i head -> nothing suspicious
Are you sure? You don't have a ref called "HEAD"? Just "HEAD".
--
Felipe Contreras
next prev parent reply other threads:[~2022-08-28 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 20:42 Ambiguous 'HEAD' issue Caglar Akyuz
2022-08-28 1:00 ` Felipe Contreras [this message]
2022-08-28 8:31 ` Caglar Akyuz
2022-08-29 6:36 ` Junio C Hamano
2022-08-29 6:57 ` Caglar Akyuz
2022-09-08 1:34 ` Jeff King
2022-09-08 6:27 ` Johannes Sixt
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=CAMP44s2iwWhpeBrzuRK5mB9ekpy4MRu5OEQ-BA4mvbUb1EJRqw@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=caglar.akyuz@sparsetechnology.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).