Skip to content

unexpected behavior for dir.clonetree #461

@JonathanTaquet

Description

@JonathanTaquet

Hi,

when using dir.clonetree('/z/y/x', '/a/b/x', file.copy) the resulting cloned folder is /a/b/x/z/y/x,
and when using dir.clonetree('/z/y/x', '/a/b', file.copy) the resulting cloned folder is /a/b/z/y/x.

Is it intended behavior ?

I would have expected dir.clonetree to act the same as cp -r, i.e. /z/y/x/foo being cloned in /a/b/x/foo in both cases.

Thanks.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions