bug#26971: mv -v output ordering looks impossible

[Pádraig Brady]

On 17/05/17 21:19, 積丹尼 Dan Jacobson wrote:
> I do
> mv -v /home/jidanni/jidanni.org/location/grow/programs /tmp

So this is working across file systems

> and see

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

create dir /tmp/programs

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

copy file grow.tgz

> removed '/home/jidanni/jidanni.org/location/grow/programs/grow.tgz'
> removed directory '/home/jidanni/jidanni.org/location/grow/programs'

obvious

> but isn't that a rather impossible sequence? At least the first two?
> Well I don't know the best way to write it.

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

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

So the create operations are implicit in the reported remove operations.
Therefore there is nothing ambiguous here I think.

cheers,
Pádraig