From fa72608677ca5465aeaa5aec3ac5ced85ed7635f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?John=20Molakvo=C3=A6?= Date: Tue, 22 Dec 2020 08:41:38 +0100 Subject: [PATCH] No more `--force-rename` --- admin_manual/configuration_server/occ_command.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/admin_manual/configuration_server/occ_command.rst b/admin_manual/configuration_server/occ_command.rst index 579b10c8c..9dbe72b9d 100644 --- a/admin_manual/configuration_server/occ_command.rst +++ b/admin_manual/configuration_server/occ_command.rst @@ -486,8 +486,7 @@ This example will list all calendars for user annie:: ``dav::move-calendar [name] [sourceuid] [destinationuid]`` allows the admin to move a calendar named ``name`` from a user ``sourceuid`` to the user ``destinationuid``. You can use the force option `-f` to enforce the move if there -are conflicts with existing shares. You can also use the `--force-rename` option to -have the system generate a new calendar name in case it already exists on the destination user. +are conflicts with existing shares. The system will also generate a new unique calendar name in case there is a conflict over the destination user. This example will move calendar named personal from user dennis to user sabine::