Displaying 3 results from an estimated 3 matches for "same_name".
Did you mean:
some_name
2002 May 04
1
A simpler move-files patch
...0, 0 },
@@ -813,6 +816,9 @@
args[ac++] = "--compare-dest";
args[ac++] = compare_dest;
}
+
+ if (move_files)
+ args[ac++] = "--move-files";
*argc = ac;
}
Index: rsync.h
--- rsync.h 2002/04/11 02:18:51 1.131
+++ rsync.h 2002/05/04 19:20:29
@@ -47,6 +47,7 @@
#define SAME_NAME SAME_DIR
#define LONG_NAME (1<<6)
#define SAME_TIME (1<<7)
+#define FLAG_NO_DELETE (1<<8)
/* update this if you make incompatible changes */
#define PROTOCOL_VERSION 26
Index: rsync.yo
--- save/rsync.yo Fri May 3 16:35:18 2002
+++ rsync.yo Sat May 4 11:53:41 2002
@@ -254,6...
2003 May 17
1
flist transmission and sorting
...). As near as i can tell this would be
unnoticeable to the protocol.
Once done the sort of the file list could be moved to
precede sending it. Thus making the sort on the receiver a
one-pass noop that could be dropped after a protocol bump.
It would also improve slightly the effectiveness of
the SAME_NAME optimisation.
With the protocol version dependant receiver non-sort the
sort order can be adjusted as necessary to produce whatever
effects are wanted in the way of duplicate removal.
Just a thought.
--
________________________________________________________________
J.W. Schultz P...
2001 Sep 01
3
Patch to make rsync preserve access times
...-----------------------------------------------------------------------
Now, on to the nasty bit of code that caused me some grief and head
scratching...
> *** ./rsync.h Sat Jan 29 18:49:36 2000
> --- ./rsync.h Sun Feb 6 20:19:53 2000
> ***************
> *** 45,53 ****
> #define SAME_NAME SAME_DIR
> #define LONG_NAME (1<<6)
> #define SAME_TIME (1<<7)
>
> /* update this if you make incompatible changes */
> ! #define PROTOCOL_VERSION 24
> #define MIN_PROTOCOL_VERSION 15
> #define MAX_PROTOCOL_VERSION 30
>
> --- 45,58 ----
>...