Displaying 4 results from an estimated 4 matches for "wupperonlin".
Did you mean:
wupperonline
2016 Jan 20
2
[PATCH] Consider nanoseconds when quick-checking for unchanged files
I wrote on Fri, 02 Jan 2015 16:02:27 +0100:
> --- a/generator.c 2014-06-14 01:05:08.000000000 +0200
> +++ b/generator.c 2015-01-02 15:50:30.000000000 +0100
> @@ -588,7 +588,14 @@
> if (ignore_times)
> return 0;
> - return cmp_time(st->st_mtime, file->modtime) == 0;
> + return cmp_time(st->st_mtime, file->modtime) ==
2016 Jan 21
0
[PATCH] Consider nanoseconds when quick-checking for unchanged files
On Thu, Dec 25, 2014 at 2:48 AM, Ingo Brückl <ib at wupperonline.de> wrote:
> On systems using nanoseconds differences should be taken into
> consideration.
>
The problem is that if you transfer from a filesystem that has nanoseconds
to one that does not support it, rsync would consider most of the files to
be constantly different, since the nanos...
2014 Dec 30
2
Modification time error
I was struggling tracking down a strange behaviour and could reproduce it
with the testsuite. After patching it with:
--- a/testsuite/compare-dest.test 2007-09-03 22:43:58.000000000 +0200
+++ b/testsuite/compare-dest.test 2014-12-30 19:28:32.060267390 +0100
@@ -18,6 +18,7 @@
# Setup the alt and chk dirs
$RSYNC -av --include=text --include='*/' --exclude='*'
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
+ ?