From 86e0e8fce1f2976f3644cfe520e8a4628f416fd7 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Sun, 28 Aug 2022 20:15:39 +0000 Subject: [PATCH] Added a comment: testremote cleanup --- ...t_3_976fd7b1db867bf5fe785e0d32acddcb._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/todo/add_testremote_cleanup/comment_3_976fd7b1db867bf5fe785e0d32acddcb._comment diff --git a/doc/todo/add_testremote_cleanup/comment_3_976fd7b1db867bf5fe785e0d32acddcb._comment b/doc/todo/add_testremote_cleanup/comment_3_976fd7b1db867bf5fe785e0d32acddcb._comment new file mode 100644 index 0000000000..da14e2a60b --- /dev/null +++ b/doc/todo/add_testremote_cleanup/comment_3_976fd7b1db867bf5fe785e0d32acddcb._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="testremote cleanup" + date="2022-08-28T20:15:38Z" + content=""" +>Like the man page for this command says, it's best to make a new remote for testing purposes, not use a production one. + +My fault for not re-reading the webpage. + +There's some value, I think, in being able to test production remotes. There's always a chance that a test remote got configured differently than a production one, so there's more confidence from having tested the production remote. + +If [find/prefer keys by file extension in key](https://git-annex.branchable.com/todo/find__47__prefer_keys_by_file_extension_in_key/) could be implemented, one could delete keys matching `*.this-is-a-test-key`. + + +"""]]