git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jason Sewall" <jasonsewall@gmail.com>
To: "Robin Rosenberg" <robin.rosenberg.lists@dewire.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Simon 'corecode' Schubert" <corecode@fs.ei.tum.de>,
	git@vger.kernel.org, raa.lkml@gmail.com
Subject: Re: [PATCH] Add a 1-second sleep to git-cvsexportcommit test
Date: Tue, 24 Jul 2007 08:31:07 -0700	[thread overview]
Message-ID: <31e9dd080707240831u1625ea70m629ea325f2101e8b@mail.gmail.com> (raw)
In-Reply-To: <200707241457.53414.robin.rosenberg.lists@dewire.com>

Fedora 7
Kernel 2.6.22 (SMP)
CVS 1.11.22
ext3 (unsure of version or how to discover version)

As one would expect from the above, the 'granularity' test you gave my
reveals 1-second granularity.

On 7/24/07, Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
> tisdag 24 juli 2007 skrev Junio C Hamano:
> > > Here CVS sleeps. The amount varies between invocations since it
> > > only sleeps enough for the seconds to wrap.
> >
> > Makes one wonder what it would do if you are on a filesystem
> > with coarser-than-a-second timestamp resolution.
>
> Like fat, but then the last test fails on FAT, which wasn't the case. Any other reasonable file
> systems that comes to your mind?
>
> Jason, could you provide us with some more information on OS, fs, cvs version etc.
>
> Whether timestamp granularity is larger than a second or not can be checked with this line, I think:
>
>         touch a && ls --full-time a && sleep 1 && touch a && ls --full-time a
>
> Sample output where the timestamps are roughly one second apart.
> -rw-r--r-- 1 me me 0 2007-07-24 14:15:47.330927250 +0200 a
> -rw-r--r-- 1 me me 0 2007-07-24 14:15:48.338990250 +0200 a
>
> -- robin
>

  reply	other threads:[~2007-07-24 15:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-22 19:41 Test #7 in t9200-git-cvsexportcommit fails Jason Sewall
2007-07-22 20:21 ` Alex Riesen
2007-07-22 20:49   ` Jason Sewall
2007-07-22 21:42     ` Alex Riesen
2007-07-22 22:19     ` Junio C Hamano
2007-07-23  3:59       ` [PATCH] Add a 1-second sleep to git-cvsexportcommit test Jason Sewall
2007-07-23  4:32         ` Junio C Hamano
2007-07-23  7:55           ` Simon 'corecode' Schubert
2007-07-24  0:23             ` Robin Rosenberg
2007-07-24  8:11               ` Simon 'corecode' Schubert
2007-07-24  8:33                 ` Robin Rosenberg
2007-07-24  8:38                   ` Simon 'corecode' Schubert
2007-07-24  9:34                     ` Robin Rosenberg
2007-07-24 10:14                       ` Junio C Hamano
2007-07-24 12:57                         ` Robin Rosenberg
2007-07-24 15:31                           ` Jason Sewall [this message]
2007-07-24 19:02                       ` Linus Torvalds
2007-07-24 22:56                         ` Robin Rosenberg
2007-07-24 23:19                           ` Linus Torvalds
2007-07-25  7:35                         ` Andy Parkins
2007-07-25  7:43                           ` Marius Storm-Olsen

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=31e9dd080707240831u1625ea70m629ea325f2101e8b@mail.gmail.com \
    --to=jasonsewall@gmail.com \
    --cc=corecode@fs.ei.tum.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=raa.lkml@gmail.com \
    --cc=robin.rosenberg.lists@dewire.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 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).