From: Adam Lee <adam8157@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: [Bug report] git log shows a wrong history
Date: Sat, 12 Nov 2022 12:23:58 +0800 [thread overview]
Message-ID: <CABAGCCq-bFYX+9kU-GGWBstjMjOcO1nSQdi6Udugtkd2McO3Tg@mail.gmail.com> (raw)
What did you do before the bug happened? (Steps to reproduce your issue)
```
git clone https://github.com/greenplum-db/gpdb-postgres-merge.git
git_log_reproducer
cd git_log_reproducer/
git co -b iteration_REL_12_12 origin/iteration_REL_12_12
git log
```
What did you expect to happen? (Expected behavior)
A part of the history is:
```
...
commit 9ac9a7fd4138988d744e0b5767883c06c20ffa6f
commit fe0a9ddbdd7eee572f7321f9680280044fd5f258
...
```
What happened instead? (Actual behavior)
That part of the history is:
```
...
commit 9ac9a7fd4138988d744e0b5767883c06c20ffa6f
commit f9c655d647427b45ae0d7bd9baf3551a013b8ea1
commit fe0a9ddbdd7eee572f7321f9680280044fd5f258
...
```
What's different between what you expected and what actually happened?
commit f9c655d647427b45ae0d7bd9baf3551a013b8ea1 is at the wrong place.
`git log --graph` is fine.
Anything else you want to add:
[System Info]
git version:
git version 2.34.1
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC
2022 x86_64
compiler info: gnuc: 11.2
libc info: glibc: 2.35
$SHELL (typically, interactive shell): /bin/bash
[Enabled Hooks]
--
Adam
next reply other threads:[~2022-11-12 4:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 4:23 Adam Lee [this message]
2022-11-12 7:13 ` [Bug report] git log shows a wrong history SZEDER Gábor
2022-11-12 8:28 ` Adam Lee
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=CABAGCCq-bFYX+9kU-GGWBstjMjOcO1nSQdi6Udugtkd2McO3Tg@mail.gmail.com \
--to=adam8157@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.
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).