Bug 2042920
Summary: | Checkout of a custom ref fails with a core dump | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Petr Šplíchal <psplicha> |
Component: | git | Assignee: | Todd Zullinger <tmz> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | amahdal, besser82, chrisw, johannes, opohorel, pstodulk, sebastian.kisela, tmz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | git-2.35.0-1.fc36 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-01-25 02:01:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Petr Šplíchal
2022-01-20 11:13:02 UTC
Thanks for the report Petr! This looks to have originated in upstream 9081a421a6 (checkout: fix "branch info" memory leaks, 2021-11-16). I sent a message upstream (with you on Cc:): https://lore.kernel.org/git/YemTGQZ97vAPUPY0@pobox.com/ Thanks for looking into this so quickly! According to the upstream discussion I see we're doing unexpected things by copying the remote ref to refs/heads. Would you recommend a better way to easily detect the default origin branch from a script within a repository where arbitrary branch is currently checked out? The use case is roughly this: git clone ... git checkout -b custom-branch ... git checkout -f <default-branch> git reset --hard origin/<default-branch> Thanks for any hint! FEDORA-2022-a63d9a0b84 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a63d9a0b84 FEDORA-2022-a63d9a0b84 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |