From: Jeff King <peff@peff.net>
To: Caglar Akyuz <caglar.akyuz@sparsetechnology.com>
Cc: Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Ambiguous 'HEAD' issue.
Date: Wed, 7 Sep 2022 21:34:22 -0400 [thread overview]
Message-ID: <YxlGnkPBmczarL62@coredump.intra.peff.net> (raw)
In-Reply-To: <AM0PR08MB432341F2A27E1133C7A31DEBFD769@AM0PR08MB4323.eurprd08.prod.outlook.com>
On Mon, Aug 29, 2022 at 06:57:00AM +0000, Caglar Akyuz wrote:
> Both 'grep HEAD .git/packed-refs' and 'git for-each-ref | grep HEAD'
> commands return nothing and still 'git status' is complaining about
> ambiguous HEAD.
Is it possible for you to tar up your .git directory and share it
(either publicly, or privately to individual developers)?
-Peff
next prev parent reply other threads:[~2022-09-08 1:34 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
2022-08-29 6:57 ` Caglar Akyuz
2022-09-08 1:34 ` Jeff King [this message]
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=YxlGnkPBmczarL62@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=caglar.akyuz@sparsetechnology.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox