"Voelker, Bernhard" writes:
> John J Foerch wrote:
>
>> So I may take up your suggestion for my own use, but I did want to put
>> forward the idea that since in my experience, trailing slash
>> interpretation is an often-mentioned stumbling-block for rsync users,
>> maybe it would be appropriate f
John J Foerch wrote:
> So I may take up your suggestion for my own use, but I did want to put
> forward the idea that since in my experience, trailing slash
> interpretation is an often-mentioned stumbling-block for rsync users,
> maybe it would be appropriate for rsync itself to provide a conveni
Wayne Davison writes:
> One solution is to install a bash script (or setup a bash function) in place
> of
> the real rsync that strips a single trailing slash from each arg. That lets
> you specify dir// if you want to copy a dir's contents. Here's one I did some
> mild tesing on and it appears
On Sat, Jan 7, 2012 at 11:19 PM, Wayne Davison wrote:
> Here's one I did some mild tesing on and it appears to work OK:
>
I just realized that script would turn the arg "/" into an empty string.
You'll want to fix that if you use the idea. Also, if you want the idiom
to be optional, you could
On Sat, Jan 7, 2012 at 6:40 PM, John J Foerch wrote:
> This is a feature request for a command-line option to disable
> special interpretation of trailing slashes on source directories.
One solution is to install a bash script (or setup a bash function) in
place of the real rsync that strips a s
My request is not to change the default behavior, but to add a new
command-line option that would effect new behavior. When one wants the
default behavior, one simply does not use the option.
Kevin Korb writes:
> I don't speak for anyone else but I would be opposed to this.
> Primarily because t
evin Korb
> Sent: Saturday, January 07, 2012 8:48 PM
> To: rsync@lists.samba.org
> Subject: Re: disable interpretation of trailing slash
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I don't speak for anyone else but I would be opposed to this.
> Primarily bec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't speak for anyone else but I would be opposed to this.
Primarily because there isn't an alternate syntax that performs the
exact same function /path/* doesn't work as expected if using --delete
(and for good reason).
On 01/07/12 21:40, John J F