🚀 go-pugleaf

      Suppose "foo" is such a node.  In
    that case "mv bar foo" should delete the existing foo (and the virtual
    hierarchy underneath it), replacing it with bar.  "mv bar foo/" should
    move bar into the directory foo, giving it the name foo/bar, and
    leaving the rest of the virtual hierarchy under foo untouched.

It follows from this that the canonical way to use mv to rename into a
directory named foo must be `mv bar foo/'.  `mv bar foo' is something
that may or may not work.

So it is proper that `mv bar foo/' work now on Unix systems.  On the
GNU system, this can work by passing `bar/' to the kernel unmodified.
But if on other systems that is not true, then on those other systems
mv needs to compensate by deleting the /.