From: Vaibhav Naik <vaibhavnaik2004@gmail.com>
To: git@vger.kernel.org
Subject: git-bugreport-2024-01-16-2051
Date: Tue, 16 Jan 2024 21:00:12 +0530 [thread overview]
Message-ID: <CALZECO2kHf_qPX06kOUPbJT_hNd5Txt9FTh_Pxr+9x_sMJdKOg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #1.2: Type: text/html, Size: 47 bytes --]
[-- Attachment #2: git-bugreport-2024-01-16-2051.txt --]
[-- Type: text/plain, Size: 2179 bytes --]
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
i typed this command in order:
git checkout ca35d53
git tag 1.1.2
git commit --allow-empty -m "want to commit at any cost"
(i just wanted to commit to catch the bug)
What did you expect to happen? (Expected behavior)
when I checkout, it was showing the commit id at the place of HEAD Point:
vaibh@VaibhavNaik MINGW64 /d/E Drive/MyCodes/Git-Testing ((ca35d53...))
and then after creating a new tag it was showing the tag name at the place of HEAD Point:
vaibh@VaibhavNaik MINGW64 /d/E Drive/MyCodes/Git-Testing ((1.1.2))
which is wrong, that place is to show where the HEAD is pointing at and not the newly created tag name
What happened instead? (Actual behavior)
It showed the newly created tag name at the place of the HEAD Point:
vaibh@VaibhavNaik MINGW64 /d/E Drive/MyCodes/Git-Testing ((1.1.2))
What's different between what you expected and what actually happened?
It should show the the detached HEAD commit id at the place of HEAD Point and not the newly created tag name
I proved this wrong by doing a commit which didn't got committed to any branch or tag but it moved the HEAD:
vaibh@VaibhavNaik MINGW64 /d/E Drive/MyCodes/Git-Testing ((newt))
$ git commit --allow-empty -m "want to commit at any cost"
[detached HEAD caad8ef] want to commit at any cost
vaibh@VaibhavNaik MINGW64 /d/E Drive/MyCodes/Git-Testing ((caad8ef...))
$ git status
HEAD detached from ca35d53
nothing to commit, working tree clean
it showed the tag name in the brackets
Anything else you want to add:
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.43.0.windows.1
cpu: x86_64
built from commit: 4b968f3ea3b32a7bc50846bab49f3f381841d297
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0 22631
compiler info: gnuc: 13.2
libc info: no libc information available
$SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe
[Enabled Hooks]
next reply other threads:[~2024-01-16 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 15:30 Vaibhav Naik [this message]
2024-01-16 19:10 ` git-bugreport-2024-01-16-2051 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALZECO2kHf_qPX06kOUPbJT_hNd5Txt9FTh_Pxr+9x_sMJdKOg@mail.gmail.com \
--to=vaibhavnaik2004@gmail.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).