[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: design question, why not always use 'cp --remove-destination'?
From: |
Jim Meyering |
Subject: |
Re: design question, why not always use 'cp --remove-destination'? |
Date: |
Tue, 22 Aug 2006 17:39:08 +0200 |
Frederik Eaton <address@hidden> wrote:
...
> The question is, is there a reason why users wouldn't always want a
> "copyFile" function to remove the destination first?
Sometimes, cp --remove-dest will fail, because the destination
cannot be removed. Yet cp without that option would be able to
update the file, because it's writable.
- design question, why not always use 'cp --remove-destination'?, Frederik Eaton, 2006/08/22
- Re: design question, why not always use 'cp --remove-destination'?, Krasimir Angelov, 2006/08/22
- Re: design question, why not always use 'cp --remove-destination'?, Eric Blake, 2006/08/22
- Re: design question, why not always use 'cp --remove-destination'?,
Jim Meyering <=
- Re: design question, why not always use 'cp --remove-destination'?, Andreas Schwab, 2006/08/22
- Re: design question, why not always use 'cp --remove-destination'?, Paul Eggert, 2006/08/22