Re: [PATCH v2 1/2] osxkeychain: lock for exclusive execution

From: Koji Nakamaru <koji.nakamaru@gree.net>
Date: May 12, 2024, 06:47 UTC
Message-ID: <CAOTNsDwMJigjZKZh74pB_TUdt=LYXO1=2RWEW0KS=_s19Y=8MQ@mail.gmail.com>
In-Reply-To: <xmqqseynisc9.fsf@gitster.g>

Thank you for the instruction about a log message. I'll follow it.

> Is this step still needed, though?

For solving the issue I originally had, just utilizing state[] to skip "store" operations is enough.

Since the osxkeychain implementation doesn't seem to be aware that it can run in parallel, I thought it would be better to leave this step in case a similar problem occurs. If this reason is weak, I'll remove this step.

Koji Nakamaru

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.