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

Re: [PATCH 2/8] Add a lockfile function to append to a file

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Apr 20, 2008, 19:43 UTC
Message-ID
<alpine.LNX.1.00.0804201528350.19665@iabervon.org>
In-Reply-To
<7vtzhxce9g.fsf@gitster.siamese.dyndns.org>
On Sat, 19 Apr 2008, Junio C Hamano wrote:
Show 13 quoted lines
> Daniel Barkalow <barkalow@iabervon.org> writes:
> 
> > This takes care of copying the original contents into the replacement
> > file after the lock is held, so that concurrent additions can't miss
> > each other's changes.
> >
> > Signed-off-by: Daniel Barkalow <barkalow@iabervon.org>
> > ---
> > How about this? Also doesn't leak a fd and catches trying to append to a 
> > file you can't read. Should I worry about mmap failing after the open?
> 
> We have copy.c to copy small existing files, while detecting failure to
> copy properly.  How about doing something like this instead?
Yeah, that's obviously the right thing to use.
	-Daniel
*This .sig left intentionally blank*
Previous: Johannes Schindelin
Message 4 of 4 in “Add a lockfile function to append to a file”
  1. 2/8 Add a lockfile function to append to a fileDaniel Barkalow, Apr 18, 2008
  2. Junio C HamanoApr 20, 2008
  3. Johannes SchindelinApr 20, 2008
  4. Daniel BarkalowApr 20, 2008

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.