From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Subject: Show of hands, how many set USE_NSEC
Date: Fri, 8 Aug 2008 09:34:55 -0700 [thread overview]
Message-ID: <20080808163455.GE9152@spearce.org> (raw)
How many users really build their Git with USE_NSEC=1?
I'm suspecting a status issue in jgit caused by jgit honoring a
millisecond resolution on file modification timestamps, and the
underlying filesystem supporting at least a 1/2 second (or finer)
granularity, but C Git was built without USE_NSEC so it only honors
1 second granularity.
This can cause jgit to think a file is locally modified as the
mtime has data in the tv_nsec field, but C Git set that to 0 in
the index as USE_NSEC wasn't enabled at build time.
I'm trying to come up with a sane way for jgit to realize it should
truncate the milliseconds out of a timestamp before it comes to
the index record.
--
Shawn.
next reply other threads:[~2008-08-08 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 16:34 Shawn O. Pearce [this message]
2008-08-08 16:55 ` Show of hands, how many set USE_NSEC Johannes Schindelin
2008-08-08 16:57 ` Shawn O. Pearce
2008-08-08 17:42 ` Linus Torvalds
2008-08-08 17:52 ` Shawn O. Pearce
2008-08-08 18:00 ` Linus Torvalds
2008-08-13 20:01 ` Robin Rosenberg
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=20080808163455.GE9152@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.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 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.