git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Kjetil Barvik <barvik@broadpark.no>
Cc: Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
	Git Mailing List <git@vger.kernel.org>,
	spearce@spearce.org
Subject: Re: [PATCH] Add core.trustlowlevelstat for diffs in dev,ino,uid and gid
Date: Sun, 26 Apr 2009 23:55:16 -0700	[thread overview]
Message-ID: <7vab628u23.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0904261159190.7331@localhost.localdomain> (Linus Torvalds's message of "Sun, 26 Apr 2009 12:25:13 -0700 (PDT)")

Linus Torvalds <torvalds@linux-foundation.org> writes:

> I started out wanting to check the stat information as much as possible, 
> but realistically, nobody probably really cares. We already effectively 
> removed st_dev checking and nsec checks.

Was ignoring st_dev checking primarily for a work tree over NFS?  I think
ignoring it makes sense.  If st_dev changes, it is likely that somebody
did a "mv" of a whole repository to some other filesystem, or the
filesystem is not giving stable st_dev to us for the whole tree---it is
not like we want to detect a change to a single path that changes its
st_dev and nothing else, as no such change is likely to be useful.

> IOW, maybe we should just do this, and remove over a hundred lines of dead 
> code or commentary/config. And never have to worry about these kinds of 
> issues with different environments again.

I like the end result.

But I am not sure about dropping the nanosecond resolution timestamps.
The area was extended recently in preparation for ext4; we can take
advantage of it to reduce the chance the racy-git avoidance codepath
triggers if we keep it.

    fba2f38 (make USE_NSEC work as expected, 2009-02-19)

    c06ff49 (Record ns-timestamps if possible, but do not use it without
    USE_NSEC, 2009-03-04)

  parent reply	other threads:[~2009-04-27  6:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-26 10:55 [PATCH] Add core.trustlowlevelstat for diffs in dev,ino,uid and gid Robin Rosenberg
2009-04-26 11:06 ` Robin Rosenberg
2009-04-26 12:06   ` [PATCH 1/2] Silence diffs due to use by non-C code Robin Rosenberg
2009-04-26 18:38   ` [PATCH] Add core.trustlowlevelstat for diffs in dev,ino,uid and gid Junio C Hamano
2009-04-26 19:25     ` Linus Torvalds
2009-04-26 22:02       ` Robin Rosenberg
2009-04-27  6:55       ` Junio C Hamano [this message]
2009-04-27 15:00         ` Linus Torvalds
2009-04-27 15:58           ` Kjetil Barvik
2010-03-14 20:51             ` Robin Rosenberg
2010-03-15  6:50               ` Junio C Hamano
2010-03-15  7:41                 ` Alex Riesen

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

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

  git send-email \
    --in-reply-to=7vab628u23.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=barvik@broadpark.no \
    --cc=git@vger.kernel.org \
    --cc=robin.rosenberg.lists@dewire.com \
    --cc=spearce@spearce.org \
    --cc=torvalds@linux-foundation.org \
    /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.
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 NNTP newsgroup(s).