Re: [PATCH 2/3] lock_ref_sha1_basic: always fill old_oid while holding lock

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Jan 13, 2016, 01:25 UTC
Message-ID: <CAPig+cRHNa8b8TdoRFsYvBBOcHbJF1VCKNgmt4SYkQsMAsJjqA@mail.gmail.com>
In-Reply-To: <20160112214439.GB2841@sigill.intra.peff.net>

On Tue, Jan 12, 2016 at 4:44 PM, Jeff King <peff@peff.net> wrote:

Show 8 quoted lines

> Our basic strategy for taking a ref lock is:
> [...]
> If these run simultaneously, we'll see a lot of lock
> contention, but each of the writes will succeed some of the
> time. The reflog may record movements between any of the
> three refs, but we would expect it to provide a consistent
> log: the "from" field of each log entry should be the same
> as the "two" field of the previous one.

s/two/to/

$ 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.