Please don't pay attention at my comment, I've realize that this is the usual behavior of GIT. My apologies to the community.
Regards, Pedro Amador El viernes, 24 de febrero de 2023 a las 22:51:18 UTC+1, Pedro Amador Rodriguez Álvarez escribió: > Hi all, > > I want to ask for help here about an strange behaviour with a repository. > I think it's strange, maybe it's a bug, or simply my lack of knowledge > > I used the `git bugreport`, so I want to share it with this community and > show my lack of git knowledge instead of send it to the > g...@vger.kernel.org list. I've using git from several years with > thousands of repositories, some of them with hundreds of developers, and > this is the first time I see a "git history" failing > > Any help will be appreciated > > $ cat git-bugreport-2023-02-24-2210.txt > 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 work in a team of 6 people: all of us make commit, merges and push. We > use "regular merges", we don't work with "rebase" > I execute "git log" to see the history of the repository > > $ git log --oneline > 2c1cbcf (HEAD -> main, origin/release/new, origin/main, origin/develop, > develop) Merged in feature/CLOUD-6915 (pull request #438) > 876ddcc (tag: v1.97.3) CLOUD-6915 Build Update "cambiar error" > e36c83a Merged in feature/CLOUD-6915 (pull request #437) > 3df874c (tag: v1.97.2) CLOUD-6915 Build: New > 5139db8 Merged in feature/change-pipeline (pull request #436) > 4dea4da (tag: v1.97.1, feature/change-pipeline) Build: Disable runner due > to the same bug > c921c76 (release/new) Merged in feature/CLOUD-6993 (pull request #435) > f440fd8 Merged in feature/CLOUD-6948 (pull request #432) > 2afc449 (tag: v1.97.0) CLOUD-6993 Fix: add " en line 25 > 7070dd0 Merged in feature/change-pipeline (pull request #434) > 69ba108 CLOUD-6993 Update: Create vnet peer and user > aaf0766 Merge branch 'release/new' into feature/change-pipeline > a2cb871 (tag: v1.96.1) CLOUD-6948 Build: New > 737983c (tag: v1.96.0) Build: Merge from develop when releasing > > > What did you expect to happen? (Expected behavior) > > I want to log from the commit "876ddcc". I expect this: > > $ git log --oneline 876ddcc > 876ddcc (tag: v1.97.3) CLOUD-6915 Build Update "cambiar error" > e36c83a Merged in feature/CLOUD-6915 (pull request #437) > 3df874c (tag: v1.97.2) CLOUD-6915 Build: New > 5139db8 Merged in feature/change-pipeline (pull request #436) > 4dea4da (tag: v1.97.1, feature/change-pipeline) Build: Disable runner due > to the same bug > c921c76 (release/new) Merged in feature/CLOUD-6993 (pull request #435) > f440fd8 Merged in feature/CLOUD-6948 (pull request #432) > 2afc449 (tag: v1.97.0) CLOUD-6993 Fix: add " en line 25 > 7070dd0 Merged in feature/change-pipeline (pull request #434) > 69ba108 CLOUD-6993 Update: Create vnet peer and user > aaf0766 Merge branch 'release/new' into feature/change-pipeline > a2cb871 (tag: v1.96.1) CLOUD-6948 Build: New > 737983c (tag: v1.96.0) Build: Merge from develop when releasing > > What happened instead? (Actual behavior) > > I obtain this response: > > $ git log --oneline 876ddcc > 876ddcc (tag: v1.97.3) CLOUD-6915 Build Update "cambiar error" > 3df874c (tag: v1.97.2) CLOUD-6915 Build: New > f440fd8 Merged in feature/CLOUD-6948 (pull request #432) > 7070dd0 Merged in feature/change-pipeline (pull request #434) > aaf0766 Merge branch 'release/new' into feature/change-pipeline > a2cb871 (tag: v1.96.1) CLOUD-6948 Build: New > 737983c (tag: v1.96.0) Build: Merge from develop when releasing > > > What's different between what you expected and what actually happened? > > There are missing commits. In the first "git log" the history is: > > 2c1cbcf -> 876ddcc -> e36c83a -> 3df874c -> 5139db8 -> 4dea4da -> c921c76 > -> f440fd8 -> 2afc449 -> 7070dd0 -> 69ba108 -> aaf0766 -> a2cb871 -> 737983c > > With the second one I obtain this sequence of commits > > 876ddcc -> 3df874c -> f440fd8 -> 7070dd0 -> aaf0766 -> a2cb871 -> 737983c > > and the expected behavior is > > 876ddcc -> e36c83a -> 3df874c -> 5139db8 -> 4dea4da -> c921c76 -> f440fd8 > -> 2afc449 -> 7070dd0 -> 69ba108 -> aaf0766 -> a2cb871 -> 737983c > > Anything else you want to add: > > I used "--oneline" to be short, but the same happend without "--oneline" > flag > > 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.37.1 (Apple Git-137.1) > cpu: arm64 > no commit associated with this build > sizeof-long: 8 > sizeof-size_t: 8 > shell-path: /bin/sh > feature: fsmonitor--daemon > uname: Darwin 22.3.0 Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST > 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000 arm64 > compiler info: clang: 14.0.0 (clang-1400.0.29.202) > libc info: no libc information available > $SHELL (typically, interactive shell): /opt/homebrew/bin/bash > > > [Enabled Hooks] > > > > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/6e04b21b-05ec-4225-b822-d8abb76eeb93n%40googlegroups.com.
