On Fri, Jun 2, 2017 at 9:56 PM, Pádraig Brady <[email protected]> wrote: > That indeed looks like a bug that has been present since the initial > implementation! > The attached should fix it up. > > thanks!
Thanks, indeed! It's not often we see bugs in tools like these that date back a quarter of a century or more. Minor suggested adjustments for NEWS: cp and mv now merely warn about any failure to preserve symlink ownership. Before, cp (without -p) would exit with a failure status, and a cross-device mv would leave such symlinks remaining in the source file system. [the bug dates back to the initial implementation]
