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

Re: broken racy detection and performance issues with nanosecond file times

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 28, 2015, 17:38 UTC
Message-ID
<xmqqbncme95a.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<5605D88A.20104@gmail.com>
Karsten Blees <karsten.blees@gmail.com> writes:
Show 10 quoted lines
> Problem 1: Failure to detect racy files (without USE_NSEC)
> ==========================================================
>
> Git may not detect racy changes when 'update-index' runs in parallel
> to work tree updates.
>
> Consider this (where timestamps are t<seconds>.<nanoseconds>):
>
>  t0.0$ echo "foo" > file1
>  t0.1$ git update-index file1 &  # runs in background
I just wonder after looking at the ampersand here ...
> Please let me know what you think of this...maybe I've completely
> screwed up and can no longer see the forest for all the trees.

... if your task would become much simpler if you declare "once you give Git the control, do not muck with the repository until you get the control back".

Previous: Johannes SchindelinNext: Karsten Blees
Message 6 of 8 in “broken racy detection and performance issues with nanosecond file times”
  1. Karsten BleesSep 25, 2015
  2. read-cache: fix file time comparisons with different precisionsKarsten Blees, Sep 28, 2015
  3. Johannes SchindelinSep 28, 2015
  4. Karsten BleesSep 29, 2015
  5. Johannes SchindelinSep 29, 2015
  6. Junio C HamanoSep 28, 2015
  7. Karsten BleesSep 29, 2015
  8. Junio C HamanoSep 28, 2015

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.