Subject: Re: bug#15232: cp -i a/s b/s c

From: [email-masked]
Date: Mon, 02 Sep 2013 08:08:55 +0800

All I know is that if it is smart enough to say
>> cp: will not overwrite just-created ‘c/s’ with ‘b/s’
which is indeed rather smart, then it should be smart enough to
gather all its thoughts together before presenting them to the user.
Hmmm, then it should be also smart enough to recognize the collision and
stop before any of it happens...

By which time the algorithm to prevent user error becomes so big as to
introduce different errors... so maybe
PB> So I'm inclined to leave this as is?
is the right thing. The only problem is five years later certain "j"
users will rediscover it and write back again expecting a free t-shirt
etc. :-)