git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC 2/5] Improve abstraction of ref lock/write.

From
Junio C Hamano <junkio@cox.net>
Date
May 17, 2006, 10:46 UTC
Message-ID
<7vk68lgc85.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060517095502.GC28529@spearce.org>
Shawn Pearce <spearce@spearce.org> writes:
Show 7 quoted lines
> Created 'struct ref_lock' to contain the data necessary to perform
> a ref update...
>
>  fetch.c |   32 +++++----
>  refs.c  |  236 ++++++++++++++++++++++++++++++---------------------------------
>  refs.h  |   24 ++++--
>  3 files changed, 144 insertions(+), 148 deletions(-)

Looks a bit intrusive probably necessary so not necessarily bad but I'll postpone looking at this for now; maybe tomorrow or more likely over the weekend.

Eyeballs from people touched the affected files in the past are greatly appreciated.

Previous: Shawn Pearce
Message 2 of 2 in “[RFC 2/5] Improve abstraction of ref lock/write.”
  1. Shawn PearceMay 17, 2006
  2. Junio C HamanoMay 17, 2006

Read the whole thread, see it on lore, or plain text.

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