From f51007d716b9dfcd514e645777b7fd33f3becea8 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 4 Apr 2022 14:27:48 -0400 Subject: [PATCH] comment --- ...mment_1_96e12b8ecba4bacfbfa5c58025bedaab._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/todo/trust_presence_info_for_specific_remotes_for_specified_time/comment_1_96e12b8ecba4bacfbfa5c58025bedaab._comment diff --git a/doc/todo/trust_presence_info_for_specific_remotes_for_specified_time/comment_1_96e12b8ecba4bacfbfa5c58025bedaab._comment b/doc/todo/trust_presence_info_for_specific_remotes_for_specified_time/comment_1_96e12b8ecba4bacfbfa5c58025bedaab._comment new file mode 100644 index 0000000000..5bcb738a57 --- /dev/null +++ b/doc/todo/trust_presence_info_for_specific_remotes_for_specified_time/comment_1_96e12b8ecba4bacfbfa5c58025bedaab._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2022-04-04T18:26:00Z" + content=""" +Using location tracking for this seems to trade off the time to contact the +remote and check presence with bloat of the git repository. This does not +strike me as a good tradeoff. If I were going to implement this, I suppose +I'd store the information in sqlite instead. + +I'm not clear what the use case or benefit of this would be? +"""]] -- 2.30.2