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. ...
N
> 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 ambig
On Wed, Jul 16, 2014 at 6:40 PM, Don Cohen
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 a filename always encode
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The solution you are missing is that rsync can archive files itself
using either --link-dest or --backup depending on whether you want a
complete tree in the archive or not.
On 07/16/2014 09:40 PM, Don Cohen wrote:
>
> It seems to me that this output
It seems to me that this output would be more useful if it
were possible to uniquely translate a line of output back into
a file path.
Right now that's not possible due to the control character encoding.
An output line like
asd\#002\#003zxc
could either mean a file of that name or
asd^B\#003zxc or
