All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] "sleep 1" sleeps too little on cygwin
Date: Wed, 18 Jan 2006 17:18:50 -0800	[thread overview]
Message-ID: <7vmzhtqakl.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060118185229.GA3001@steel.home> (Alex Riesen's message of "Wed, 18 Jan 2006 19:52:29 +0100")

Alex Riesen <raa.lkml@gmail.com> writes:

> this is probable unsafe too: not all systems export inodes
> (the recent cygwin breakage comes to mind).

Hmph.  I thought that breakage was about struct dirent, not what
we read from struct stat; d_ino is XSI extension so that may
have been the reason cygwin folks removed it, but st_ino is in
BASE --- did they remove that as well?

But you are right.  Among "struct stat" members, only S_IFMT
part from st_mode and st_size are meaningful for symlinks after
lstat() and other members are unspecified.  Which means that, in
the strictest sense, the original test that tried to see if the
timestamp change makes the entry for the symlink cache-dirty,
was pointless.

HOWEVER.

We live in the real world, not in a strict POSIX world.  We (the
index file) relies on lstat() to update st_mtime and/or st_ino,
and I think it is OK (IOW, we declare that platforms on which we
cannot rely on these members are not worth supporting).


By the way, if you have an access to git on cygwin with FAT,
could you test your patch ($SECONDS) and then i-num patch (the
machine with cygwin I can borrow has only NTFS) please?

  reply	other threads:[~2006-01-19  1:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 11:25 [PATCH] "sleep 1" sleeps too little on cygwin Alex Riesen
2006-01-18  1:41 ` Junio C Hamano
2006-01-18 13:50   ` Alex Riesen
2006-01-18 16:55     ` Junio C Hamano
2006-01-19  5:18   ` Christopher Faylor
2006-01-18  8:53 ` Junio C Hamano
2006-01-18 11:35   ` Johannes Schindelin
2006-01-18 17:00     ` Junio C Hamano
2006-01-18 18:52       ` Alex Riesen
2006-01-19  1:18         ` Junio C Hamano [this message]
2006-01-19  5:20           ` Christopher Faylor
2006-01-19 15:01           ` Alex Riesen
2006-01-19 18:24             ` Junio C Hamano
2006-01-19 22:13               ` Alex Riesen
2006-01-20  1:13                 ` Junio C Hamano
2006-01-19 18:28             ` Christopher Faylor
2006-01-19 22:12               ` Alex Riesen
2006-01-19 22:25                 ` Christopher Faylor
2006-01-20  1:13                   ` Junio C Hamano
2006-01-20  3:35                     ` Christopher Faylor
2006-01-20 15:23                       ` Alex Riesen
2006-01-20 15:40                         ` Christopher Faylor

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=7vmzhtqakl.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.