Thanks.
Jerry _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
I searched around gnu.org, and searched this list back to the start of
2006, for info on why cp --reply is deprecated (and will be removed in
2008). Sorry if this has been asked before... but what's the
replacement for cp -i --reply=no ? I use it, for instance, when I'd
started a long-running recursive directory copy that was interrupted in
the middle and I want to re-start cp to finish the job. Using
--reply=no tells cp not to overwrite existing files; it saves a lot of
useless re-copying.
- Replacement for cp -i --reply=no ? Jerry Peek
- Re: Replacement for cp -i --reply=no ? Andreas Schwab
- Re: Replacement for cp -i --reply=no ? Jerry Peek
- Re: Replacement for cp -i --reply=no ? Bob Proulx
