Jerry Peek <[EMAIL PROTECTED]> writes: > 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 ?
IMHO the best replacement is rsync. > 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. cp -u does that as well. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
