Re: Skip based on checksum not worked as expected when using with complex filter rules.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, I am assuming that without --itemize-changes you couldn't tell the difference between I am transferring a file and I am fixing the timestamp on a file. Even if I am right, you are probably still mis-using --checksum. When you use --checksum you

Is it possiable to suppress the site-specified messages?

Hi all, When connect to a remote rsync server, ofter it will give some site- specified messages, say, the following one: ___ | University of Science and Technology of China | | Open Source Mirror

Re: Skip based on checksum not worked as expected when using with complex filter rules.

On Fri, 17 Apr 2015 23:45:42 -0400, Kevin Korb wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, I am assuming that without --itemize-changes you couldn't tell the difference between I am transferring a file and I am fixing the timestamp on a file. Even if I am right, you are

Re: Skip based on checksum not worked as expected when using with complex filter rules.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I still don't see an output from rsync --itemize-changes with an A/B difference. On 04/18/2015 12:15 AM, Hongyi Zhao wrote: On Fri, 17 Apr 2015 23:45:42 -0400, Kevin Korb wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, I am assuming

Re: Skip based on checksum not worked as expected when using with complex filter rules.

On Sat, 18 Apr 2015 00:39:42 -0400, Kevin Korb wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I still don't see an output from rsync --itemize-changes with an A/B difference. What do you mean by saying the above things? Do you mean only the `--itemize-changes' is enough for my

Re: Skip based on checksum not worked as expected when using with complex filter rules.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I mean that a listing of a /path/to/filename is utterly useless. - --itemize-changes specifies why a particular /path/to/filename is listed.It also describes what will happen to that file. All in a very short string of characters. Simply put,

Re: Skip based on checksum not worked as expected when using with complex filter rules.

On Sat, 18 Apr 2015 01:10:41 -0400, Kevin Korb wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I mean that a listing of a /path/to/filename is utterly useless. - --itemize-changes specifies why a particular /path/to/filename is listed.It also describes what will happen to that file.

On the case `an identical item replaces the dots with spaces' for `--itemize-changes'.

Hi all, The `--itemize-changes' has the following notes within the manual: The other letters in the string above are the actual letters that will be output if the associated attribute for the item is being updated or a . for no change. Three exceptions to this

Re: Skip based on checksum not worked as expected when using with complex filter rules.

On Fri, 17 Apr 2015 21:27:56 -0400, Kevin Korb wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Any time rsync wants to do something to a file you don't think it should be see what --itemize-changes says about it. In fact, -v is almost entirely useless without --itemize-changes. In

Re: Skip based on checksum not worked as expected when using with complex filter rules.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Any time rsync wants to do something to a file you don't think it should be see what --itemize-changes says about it. In fact, -v is almost entirely useless without --itemize-changes. In fact, if I was in charge I would make -v include

Skip based on checksum not worked as expected when using with complex filter rules.

Hi all, I've a local repository for Debian, and I'm doing some rsync testings on it. See the following commands for detail: werner@debian:~/software/LocalRepo$ rsync -amvHKLPRSB131072 -n \ ftp.uk.debian.org::debian/./dists/wheezy-updates/main/\ debian-installer/binary-amd64/Packages.gz \