threads / bug / 59593

Git bug.

Subject: Git bug.

## tl;dr

2 messages between Apr 14, 2023 and Apr 14, 2023.

replies: 1people: 2as markdown or json

Gabriel Furstenheim Milerud· Apr 14, 2023, 08:29 UTC · lore

Hi, Sorry if this is not the right address to report bugs. I'm following https://stackoverflow.com/questions/10728104/where-can-i-report-a-git-bug/10733251#10733251

Cheers Gabriel Fürstenheim

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)
> repository in branch A
git name-rev $(git rev-parse HEAD) --name-only
> returns A

git checkout B git name-rev $(git rev-parse HEAD) --name-only

What did you expect to happen? (Expected behavior) It should return B

What happened instead? (Actual behavior) It returns A

What's different between what you expected and what actually happened? git rev-parse does not seem to update. Same is happenning with git rev-parse @{-1}

Anything else you want to add: git version 2.34.1

I recently migrated to ubuntu 22. In ubuntu 18 with previous git version is was working as expected.

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.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.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 compiler info: gnuc: 11.3 libc info: glibc: 2.35 $SHELL (typically, interactive shell): /bin/bash

[Enabled Hooks]
Kristoffer Haugsbakk· Apr 14, 2023, 09:26 UTC · re: Gabriel Furstenheim Milerud · lore

Re: Git bug.

On Fri, Apr 14, 2023, at 10:29, Gabriel Furstenheim Milerud wrote:
> Hi,
> Sorry if this is not the right address to report bugs. I'm following
> https://stackoverflow.com/questions/10728104/where-can-i-report-a-git-bug/10733251#10733251
LGTM.

VonC has amazing Git answers on SO, but I feel that this changelog-type answer is *too much* for a procedure which is just (based on the bug reports from the last month or so):

1. Run `git bugreport`
2. Edit the file by filling out the blanks and removing irrelevant stuff
   (follow the instructions)
3. Post the report as an inline plaintext email
So basically the sibling answer https://stackoverflow.com/a/70175922/1725151
-- 
Kristoffer Haugsbakk

← back to recent threads