From: Junio C Hamano <gitster@pobox.com>
To: Caglar Akyuz <caglar.akyuz@sparsetechnology.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Ambiguous 'HEAD' issue.
Date: Sun, 28 Aug 2022 23:36:23 -0700 [thread overview]
Message-ID: <xmqqsflfr1y0.fsf@gitster.g> (raw)
In-Reply-To: AM0PR08MB4323160241D4341FB1B99CC2FD749@AM0PR08MB4323.eurprd08.prod.outlook.com
Caglar Akyuz <caglar.akyuz@sparsetechnology.com> writes:
> * find . -name HEAD | grep -v modules -> only .git/logs/HEAD and .git/HEAD
plus "grep HEAD .git/packed-refs"
> * git branch -a | grep HEAD -> nothing
plus "git for-each-ref | grep HEAD"
next prev parent reply other threads:[~2022-08-29 6:36 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
2022-08-28 8:31 ` Caglar Akyuz
2022-08-29 6:36 ` Junio C Hamano [this message]
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=xmqqsflfr1y0.fsf@gitster.g \
--to=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.