On Fri, Jun 24, 2005 at 11:17:20AM -0600, you wrote:
The second option that I recommend is to deprecate this option
entirely and remove it from the code base.
I think it's safe to say that a number of these utilities have gotten
more flags than they strictly need. Pruning may be a good thing.
The longer it remains the harder it will be to change to better
behavior later.
Making mv do everything people want when they want is a hopeless cause,
made harder by the fact that some of the oddness is a posix requirement.
I'd say that if someone has a nify feature they can't live without, it
is time for a new command with a new name, without compatability
baggage. Maybe call it mv++.
Mike Stone
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
