{"thread":{"id":"59593","subject":"Git bug.","startedAt":"2023-04-14T08:30:19Z","lastAt":"2023-04-14T09:26:59Z","messageCount":2,"participants":["Gabriel Furstenheim Milerud","Kristoffer Haugsbakk"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"475349","messageId":"CAJN3DWqbR-9sNGT=Njei5PNSGKVKSOgrY4K=FXVjUKEFQ27bWg@mail.gmail.com","threadId":"59593","inReplyTo":null,"subject":"Git bug.","fromName":"Gabriel Furstenheim Milerud","fromEmail":"furstenheim@gmail.com","sentAt":"2023-04-14T08:29:21Z","receivedAt":"2023-04-14T08:30:19Z","isPatch":false,"sender":{"key":"furstenheim@gmail.com","avatar":null},"body":"Hi,\nSorry if this is not the right address to report bugs. I'm following\nhttps://stackoverflow.com/questions/10728104/where-can-i-report-a-git-bug/10733251#10733251\n\nCheers\nGabriel Fürstenheim\n\n\nThank you for filling out a Git bug report!\nPlease answer the following questions to help us understand your issue.\n\nWhat did you do before the bug happened? (Steps to reproduce your issue)\n> repository in branch A\ngit name-rev $(git rev-parse HEAD) --name-only\n> returns A\ngit checkout B\ngit name-rev $(git rev-parse HEAD) --name-only\n\n\n\nWhat did you expect to happen? (Expected behavior)\nIt should return B\n\nWhat happened instead? (Actual behavior)\nIt returns A\n\nWhat's different between what you expected and what actually happened?\ngit rev-parse does not seem to update. Same is happenning with git rev-parse @{-1}\n\nAnything else you want to add:\ngit version 2.34.1\n\nI recently migrated to ubuntu 22. In ubuntu 18 with previous git version is was working as expected.\n\nPlease review the rest of the bug report below.\nYou can delete any lines you don't wish to share.\n\n\n[System Info]\ngit version:\ngit version 2.34.1\ncpu: x86_64\nno commit associated with this build\nsizeof-long: 8\nsizeof-size_t: 8\nshell-path: /bin/sh\nuname: Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64\ncompiler info: gnuc: 11.3\nlibc info: glibc: 2.35\n$SHELL (typically, interactive shell): /bin/bash\n\n\n[Enabled Hooks]\n"},{"id":"475350","messageId":"fe75dd24-344b-4c9b-b08f-af12f3beff11@app.fastmail.com","threadId":"59593","inReplyTo":"CAJN3DWqbR-9sNGT=Njei5PNSGKVKSOgrY4K=FXVjUKEFQ27bWg@mail.gmail.com","subject":"Re: Git bug.","fromName":"Kristoffer Haugsbakk","fromEmail":"code@khaugsbakk.name","sentAt":"2023-04-14T09:26:30Z","receivedAt":"2023-04-14T09:26:59Z","isPatch":false,"sender":{"key":"code@khaugsbakk.name","avatar":"https://avatars.githubusercontent.com/u/2229597?v=4"},"body":"On Fri, Apr 14, 2023, at 10:29, Gabriel Furstenheim Milerud wrote:\n> Hi,\n> Sorry if this is not the right address to report bugs. I'm following\n> https://stackoverflow.com/questions/10728104/where-can-i-report-a-git-bug/10733251#10733251\n\nLGTM.\n\nVonC has amazing Git answers on SO, but I feel that this changelog-type\nanswer is *too much* for a procedure which is just (based on the bug\nreports from the last month or so):\n\n1. Run `git bugreport`\n2. Edit the file by filling out the blanks and removing irrelevant stuff\n   (follow the instructions)\n3. Post the report as an inline plaintext email\n\nSo basically the sibling answer https://stackoverflow.com/a/70175922/1725151\n\n-- \nKristoffer Haugsbakk\n"}]}