From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org, Christopher Faylor <me@cgf.cx>
Subject: Re: [PATCH] "sleep 1" sleeps too little on cygwin
Date: Thu, 19 Jan 2006 23:13:46 +0100 [thread overview]
Message-ID: <20060119221346.GC3601@steel.home> (raw)
In-Reply-To: <7vr774dqjo.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano, Thu, Jan 19, 2006 19:24:27 +0100:
>
> > Works if sleep is for 2 secs (I completely forgot about that stupid
> > FAT granularity!)
> > st_ino is always the same (it is a hash of pathname).
> > Christopher, how is that supposed to work with hardlinks? (NTFS has
> > hardlinks, BTW)
>
> So the verdict is to take your patch but wait for three seconds?
> I still have mild aversion about $SECONDS though...
>
Maybe just wait for 3 (three) seconds? It should guarantee the change
in mtime.
next prev parent reply other threads:[~2006-01-19 22:15 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
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 [this message]
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=20060119221346.GC3601@steel.home \
--to=raa.lkml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=me@cgf.cx \
/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).