From: Patrick Steinhardt <ps@pks.im>
To: Yonatan Roth <yroth@paloaltonetworks.com>
Cc: git@vger.kernel.org
Subject: Re: ISSUE - Sequential execution failure - Lock auto created between git commands
Date: Mon, 26 May 2025 15:23:07 +0200 [thread overview]
Message-ID: <aDRrO4x0o0Hit6au@pks.im> (raw)
In-Reply-To: <CAJR-fbZ4X1+gN75m2dUvocR6NkowLOZ9F26cjBy8w1qd181OoQ@mail.gmail.com>
On Sun, May 25, 2025 at 05:13:30PM +0300, Yonatan Roth wrote:
> Hi,
>
>
> Using a script we run the following set of git commands:
>
> git branch -a
>
> git remote -v
>
> git stash push --all --include-untracked
>
> git checkout test_git_ver
>
> git remote -v
>
> git fetch
>
> git status --branch --porcelain=v1 -u
>
> git checkout test_git_ver_workspace
>
>
>
>
> After upgrading the git version to - *2.47.2*, we started getting the
> following error:
>
> error: cannot lock ref 'HEAD': Unable to create '.../.git/*HEAD.lock*':
> File exists.
This sounds similar to the issue reported in [1], please see my reply
there. I'll send a patch series the over the next days to address the
issue.
Patrick
[1]: <CANi7bVAkNc+gY1NoXfJuDRjxjZLTgL8Lfn8_ZmWsvLAoiLPkNg@mail.gmail.com>
prev parent reply other threads:[~2025-05-26 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 14:13 ISSUE - Sequential execution failure - Lock auto created between git commands Yonatan Roth
2025-05-26 13:23 ` Patrick Steinhardt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aDRrO4x0o0Hit6au@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=yroth@paloaltonetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).