Subject: | |
From: | |
Reply To: | |
Date: | Sat, 7 Mar 2015 12:05:36 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On 03/07/2015 03:32 AM, David Sommerseth wrote:
>
>> From: "ToddAndMargo" <[log in to unmask]>
>> To: "SCIENTIFIC-LINUX-USERS" <[log in to unmask]>
>> Sent: 7. March 2015 05:40:43
>> Subject: Re: need rsync exclude help
>>
>>> --exclude='{wine-*,wine-1.7.24}' /home/CDs/Linux /mnt/MyCDs/.
>>>
>>
>> I am not real certain that the {} thingy works correctly.
>> Anyway, I only needed 'wine-*'
>
> That seems redundant in this case. You can always test such expansions using 'echo'
>
> $ echo {wine-*,wine-1.7.24}
> wine-* wine-1.7.24
> $ echo wine-{1.7.24,package-1.2.3}
> wine-1.7.24 wine-package-1.2.3
>
> Here I also added a little demonstration of how the {} expansion can work.
>
>
> --
> kind regards,
>
> David SOmmerseth
>
Hi David,
Yes, it was redundant. I wanted to see if the syntax crashed.
I also set up a bunch of wine-1.7.xx directories to see if
they too would be left alone.
When I tried the expansion in the rsync string, it did not
work, so I went back to just
--exclude='wine-*'
-T
Sweet examples. Thank you!
I don't know if it is just me but I can have thins
explained to me for hours and not get it, but show
me an example and I am off to the races. I guess
it is just different ways different folks learn.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|