bug#26971: mv -v output ordering looks impossible

[積丹尼 Dan Jacobson]

PB> So this is working across file systems
Yes.
>> '/home/jidanni/jidanni.org/location/grow/programs' -> '/tmp/programs'
This says to me "I, the mv command, have just moved  A to B.

PB> create dir /tmp/programs
If that (create B) is what it is doing in that step, then it should not
mention the unrelated A.

>> '/home/jidanni/jidanni.org/location/grow/programs/grow.tgz' -> 
>> '/tmp/programs/grow.tgz'
This says to me "I am moving A/C to B/C". But there is no more A... at
least that is what the user thinks... so how could it still move it.


PB> I suppose we could distinguish the creation operations, though
PB> note if the first attempted rename() worked for the source dir,
PB> then there would have been just a single operation output like:

PB>   '/home/jidanni/jidanni.org/location/grow/programs' -> '/tmp/programs'

Well all I know is if the user always can do something on one line, then he
would expect a consistent number of -v output lines.