Displaying 2 results from an estimated 2 matches for "1917gmt".
2016 Jan 25
0
[Bug 11521] rsync does not use high-resolution timestamps to determine file differences
...6-01-24 22:57:53.000000000 -0500 3/bar
1321176 -rw-r--r-- 6 user user 0 2016-01-24 22:57:53.000000000 -0500 3/foo
1321176 -rw-r--r-- 6 user user 0 2016-01-24 22:57:53.000000000 -0500 4/bar
1321176 -rw-r--r-- 6 user user 0 2016-01-24 22:57:53.000000000 -0500 4/foo
23:00:38 ~/T$ ~/rsync-HEAD-20160124-1917GMT/rsync -aviH --link-dest ../2/ 1/ 5/
sending incremental file list
.d..t...... ./
sent 89 bytes received 19 bytes 216.00 bytes/sec
total size is 0 speedup is 0.00
23:00:56 ~/T$ lat */*
1321175 -rw-r--r-- 2 user user 0 2016-01-24 22:57:53.013689572 -0500 1/bar
1321175 -rw-r--r-- 2 user user 0 201...
2014 Dec 25
8
[PATCH] Consider nanoseconds when quick-checking for unchanged files
On systems using nanoseconds differences should be taken into consideration.
--- a/generator.c 2014-06-14 01:05:08.000000000 +0200
+++ b/generator.c 2014-12-25 11:19:54.000000000 +0100
@@ -588,7 +588,13 @@
if (ignore_times)
return 0;
- return cmp_time(st->st_mtime, file->modtime) == 0;
+ return cmp_time(st->st_mtime, file->modtime) == 0
+#ifdef ST_MTIME_NSEC
+ ?