From: "Enis Bayramoğlu" <enis@picussecurity.com>
To: git@vger.kernel.org
Subject: `git status` output is very misleading after a merge on a "detached HEAD"
Date: Tue, 11 Apr 2017 11:57:00 +0300 [thread overview]
Message-ID: <CAMLReHYBVmuu5H015N1ShCD0iLNau9oLOabJhQ7xc=58rXQi+Q@mail.gmail.com> (raw)
I've encountered a very misleading output from `git status`. Here's a
sequence of events that demonstrates the issue:
$ git --version
git version 2.12.0
$ git checkout origin/master
$ git status
HEAD detached from origin/master
nothing to commit, working directory clean
$ git merge --ff f3515b749be861b57fc70c2341c1234eeb0d5b87
$ git status
HEAD detached from origin/master
nothing to commit, working directory clean
$ git rev-parse origin/master
e1dc1baaadee0f1aef2d5c45d068306025d11f67
$ git rev-parse HEAD
786cb6dd09897e0950a2bdc971f0665a059efd33
I think it's extremely misleading that `git status` simply reports
"HEAD detached from origin/master" while this simply happens to be a
mildly relevant fact about some past state.
Thanks and regards
next reply other threads:[~2017-04-11 8:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 8:57 Enis Bayramoğlu [this message]
2017-04-11 14:55 ` `git status` output is very misleading after a merge on a "detached HEAD" Michael J Gruber
2017-04-11 15:13 ` Enis Bayramoğlu
2017-04-11 20:40 ` Ævar Arnfjörð Bjarmason
2017-04-12 5:43 ` Michael J Gruber
2017-04-12 6:15 ` Enis Bayramoğlu
2017-04-12 11:36 ` Michael J Gruber
2017-04-12 12:18 ` Ævar Arnfjörð Bjarmason
2017-04-12 13:11 ` Michael J Gruber
2017-04-12 13:30 ` Ævar Arnfjörð Bjarmason
2017-04-14 16:25 ` Philip Oakley
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='CAMLReHYBVmuu5H015N1ShCD0iLNau9oLOabJhQ7xc=58rXQi+Q@mail.gmail.com' \
--to=enis@picussecurity.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).