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
