From 60f984933672b6ae36610aa9297e44d08dffb838 Mon Sep 17 00:00:00 2001 From: infectormp Date: Thu, 19 Apr 2018 16:29:47 +0300 Subject: [PATCH] docs: Improve borg with-lock (#3780) docs: improve borg with-lock, link to FAQ --- docs/usage/with-lock.rst.inc | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/usage/with-lock.rst.inc b/docs/usage/with-lock.rst.inc index 6f4fc741a..32368d549 100644 --- a/docs/usage/with-lock.rst.inc +++ b/docs/usage/with-lock.rst.inc @@ -57,9 +57,5 @@ running in the repo), then execute the given command as a subprocess and wait for its termination, release the lock and return the user command's return code as borg's return code. -.. note:: - - If you copy a repository with the lock held, the lock will be present in - the copy. Thus, before using borg on the copy from a different host, - you need to use "borg break-lock" on the copied repository, because - Borg is cautious and does not automatically remove stale locks made by a different host. \ No newline at end of file +As example you can use "borg with-lock" to copy a repo to another location +(see :ref:`can_i_copy_or_synchronize_my_repo_to_another_location` in the FAQ).