From 6356491919593b98d5a5573f05d6660e75a4963e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 8 Nov 2017 13:02:42 -0400 Subject: improve testremote docs --- doc/git-annex-testremote.mdwn | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/doc/git-annex-testremote.mdwn b/doc/git-annex-testremote.mdwn index fff08fdcc..5c3a5ca5b 100644 --- a/doc/git-annex-testremote.mdwn +++ b/doc/git-annex-testremote.mdwn @@ -14,9 +14,12 @@ the remote, then redownloading them, removing them from the remote, etc. It's safe to run in an existing repository (the repository contents are not altered), although it may perform expensive data transfers. -Testing a single remote will use the remote's configuration, -automatically varying the chunk sizes, and with simple shared encryption -enabled and disabled. +It's best to make a new remote for testing purposes. While the test +tries to clean up after itself, if the remote being tested had a bug, +the cleanup might fail, leaving test data in the remote. + +Testing will use the remote's configuration, automatically varying +the chunk sizes, and with simple shared encryption enabled and disabled. # OPTIONS -- cgit v1.2.3