martin f krafft <[EMAIL PROTECTED]> wrote: > also sprach Jim Meyering <[EMAIL PROTECTED]> [2006.08.18.1630 +0100]: >> Why don't you just do "mv a/* foo/a", if that's what you want? > > When the task is to integrate one hiararchy with another, and some > target dirs are already present, others are not, the above is not > feasible.
Use another tool, like rsync or cp --update. The other day, someone wanted to add a feature to cut, making it accept an option meaning "use a sequence of white space as the delimiter". The response was "use gawk, or perl, or ruby, or ...". If we were to add every new feature (especially when some other tool does the job better), the *core*utils would have become monstrous and unmaintainable long ago. >> I doubt GNU mv will ever do something like that for you, given the >> command "mv a foo". > > Why not? Is there actually a technical reason for not supporting > this? In my view, it's an enhancement for those who need it without > getting into someone else's way. And I doubt people actually rely on > /bin/mv to find out when a non-empty target directory already > exists. Changing the default behavior of a tool like mv is never done lightly. And adding a new option would be almost as hard to justify. If you're convinced this is something that should change, please post to [email protected] with your justification. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
