git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Karsten Blees <karsten.blees@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: broken racy detection and performance issues with nanosecond file times
Date: Mon, 28 Sep 2015 10:38:57 -0700	[thread overview]
Message-ID: <xmqqbncme95a.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <5605D88A.20104@gmail.com> (Karsten Blees's message of "Sat, 26 Sep 2015 01:28:10 +0200")

Karsten Blees <karsten.blees@gmail.com> writes:

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

  parent reply	other threads:[~2015-09-28 17:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25 23:28 broken racy detection and performance issues with nanosecond file times Karsten Blees
2015-09-28 10:39 ` [PATCH/RFC] read-cache: fix file time comparisons with different precisions Karsten Blees
2015-09-28 12:52   ` Johannes Schindelin
2015-09-29 10:23     ` Karsten Blees
2015-09-29 13:42       ` Johannes Schindelin
2015-09-28 17:38 ` Junio C Hamano [this message]
2015-09-29 11:28   ` broken racy detection and performance issues with nanosecond file times Karsten Blees
2015-09-28 18:17 ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqbncme95a.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=karsten.blees@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).