From: Dana Dahlstrom <dahlstrom@google.com>
To: git@vger.kernel.org
Subject: 'HEAD' is not a commit (according to git-checkout)
Date: Thu, 21 May 2020 12:00:00 -0700 [thread overview]
Message-ID: <CACqwCQiLpZ1HFzgJw0p0KR3jXNsxkhjXmF_huzhv+qkMZmybBQ@mail.gmail.com> (raw)
What did you do before the bug happened? (Steps to reproduce your issue)
$ git clone https://github.com/githubtraining/hellogitworld.git
$ cd hellogitworld
$ git checkout -b work -t master HEAD
fatal: 'HEAD' is not a commit and a branch 'work' cannot be created from it
$ git show -s --oneline
ef7bebf (HEAD -> master, origin/master, origin/HEAD) Fix groupId […]
$ git checkout -b work -t master ef7bebf
fatal: 'ef7bebf' is not a commit and a branch 'work' cannot be created from it
What did you expect to happen? (Expected behavior)
I expected a new branch named 'work' to be created and checked out,
pointing to commit ef7bebf and with upstream branch set to 'master'.
What happened instead? (Actual behavior)
I saw these erroneous messages (copied from above):
fatal: 'HEAD' is not a commit and a branch 'work' cannot be created from it
fatal: 'ef7bebf' is not a commit and a branch 'work' cannot be created from it
What's different between what you expected and what actually happened?
I expected a new branch but instead saw erroneous messages.
Anything else you want to add:
This question seems to show the same problem:
stackoverflow.com/questions/48671851
[System Info]
git version:
git version 2.27.0.rc0.183.gde8f92d652-goog
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
uname: Linux 5.2.17-1rodete3-amd64 #1 SMP Debian 5.2.17-1rodete3
(2019-10-21 > 2018) x86_64
compiler info: gnuc: 8.3
libc info: glibc: 2.29
next reply other threads:[~2020-05-21 19:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 19:00 Dana Dahlstrom [this message]
2020-05-21 19:16 ` 'HEAD' is not a commit (according to git-checkout) Jeff King
2020-05-23 7:07 ` René Scharfe
2020-05-23 16:29 ` Jeff King
2020-05-24 7:22 ` [PATCH 1/2] checkout: add tests for -b and --track René Scharfe
2020-05-27 6:40 ` Jeff King
2020-05-28 13:53 ` René Scharfe
2020-05-24 7:23 ` [PATCH 2/2] checkout: improve error messages for -b with extra argument René Scharfe
2020-05-27 6:42 ` Jeff King
2020-05-24 7:23 ` 'HEAD' is not a commit (according to git-checkout) René Scharfe
2020-05-24 16:15 ` Junio C Hamano
2020-05-27 6:52 ` Jeff King
2020-05-27 15:44 ` Junio C Hamano
2020-05-27 15:52 ` Randall S. Becker
2020-05-27 17:31 ` Jeff King
2020-05-21 19:49 ` René Scharfe
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=CACqwCQiLpZ1HFzgJw0p0KR3jXNsxkhjXmF_huzhv+qkMZmybBQ@mail.gmail.com \
--to=dahlstrom@google.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.
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).