Re: question about output of files copied/deleted

2014-07-17 Thread Wayne Davison
On Wed, Jul 16, 2014 at 6:40 PM, Don Cohen don-rs...@isis.cs3-inc.com wrote: An output line like asd\#002\#003zxc could either mean a file of that name or asd^B\#003zxc or asd^B^Czxc or asd\#002^Czxc Did you test that theory? Give it a try and you'll discover that \# followed by 3 digits in

Re: question about output of files copied/deleted

2014-07-17 Thread Don Cohen
An output line like asd\#002\#003zxc could either mean a file of that name or asd^B\#003zxc or asd^B^Czxc or asd\#002^Czxc Did you test that theory? Give it a try and you'll discover that \# followed by 3 digits in a filename always encodes the backslash, so there is never an

Re: question about output of files copied/deleted

2014-07-17 Thread Francis . Montagnac
Hi. On Wed, 16 Jul 2014 23:24:45 -0700 Don Cohen wrote: So another question/suggestion - if you save the output it would be nice to be able to pipe it back into rsync as the list of files to be transferred - which would be easier if there were a switch to do the translation above. ... Not

[Bug 10724] New: rsync 3.1.1 incorrectly creates extra dirs inside --backup-dir on Mac OSX

2014-07-17 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10724 Summary: rsync 3.1.1 incorrectly creates extra dirs inside --backup-dir on Mac OSX Product: rsync Version: 3.1.1 Platform: x86 OS/Version: Mac OS X Status: NEW

[Bug 10724] rsync 3.1.1 incorrectly creates extra dirs inside --backup-dir on Mac OSX

2014-07-17 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10724 --- Comment #1 from chd...@gmail.com 2014-07-18 03:28:52 UTC --- My apologies, this bug is also present on rsync 3.1.0. I still think it's a bug. Also, I was almost right; it didn't work like this on 3.0.9 and earlier. -- Configure bugmail:

[Bug 10724] rsync 3.1.1 incorrectly creates extra dirs inside --backup-dir on Mac OSX

2014-07-17 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10724 --- Comment #2 from chd...@gmail.com 2014-07-18 04:26:08 UTC --- For fun I cloned the git repo and bisected. The first commit that exhibits the aforementioned buggy behavior is: 3696674bc62b0c1250027dbeedafdd7ebafdcf8b which carries the