From 78f31022e35d2c8d6ba4f58e772fe4072bd3f80e Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Wed, 21 Apr 2021 15:37:38 +0000 Subject: [PATCH] Added a comment: auto-expire temp repos --- .../comment_3_64ba3f1d5099e066d554566ca818bdd6._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/hiding_a_repository/comment_3_64ba3f1d5099e066d554566ca818bdd6._comment diff --git a/doc/todo/hiding_a_repository/comment_3_64ba3f1d5099e066d554566ca818bdd6._comment b/doc/todo/hiding_a_repository/comment_3_64ba3f1d5099e066d554566ca818bdd6._comment new file mode 100644 index 0000000000..fcc0579327 --- /dev/null +++ b/doc/todo/hiding_a_repository/comment_3_64ba3f1d5099e066d554566ca818bdd6._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="auto-expire temp repos" + date="2021-04-21T15:37:37Z" + content=""" +As a possible simpler alternative, maybe add an option to [[git-annex-dead]] to mark a repo dead from a future time onwards? I often have temp repos created on temp cloud instances. I mark them untrusted right after cloning, and then manually mark them dead after the cloud instance is gone. If the latter part were automated, would that cover most of what hidden repos do? +"""]] -- 2.30.2