From bc70a8b3f6e18ddabcc68008cb4db6ad44a8b91a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 1 Jan 2020 15:03:01 -0400 Subject: [PATCH] comments --- ...t_11_5c1ea2e8ac475d8c0ddca2c38f968b95._comment | 13 +++++++++++++ ...nt_4_8708bf0aef0025e2ed1a8b9d2a7f0112._comment | 15 +++++++++++++++ 2 files changed, 28 insertions(+) create mode 100644 doc/git-annex-unused/comment_11_5c1ea2e8ac475d8c0ddca2c38f968b95._comment create mode 100644 doc/todo/git-annex-cat/comment_4_8708bf0aef0025e2ed1a8b9d2a7f0112._comment diff --git a/doc/git-annex-unused/comment_11_5c1ea2e8ac475d8c0ddca2c38f968b95._comment b/doc/git-annex-unused/comment_11_5c1ea2e8ac475d8c0ddca2c38f968b95._comment new file mode 100644 index 0000000000..9c0c594fc5 --- /dev/null +++ b/doc/git-annex-unused/comment_11_5c1ea2e8ac475d8c0ddca2c38f968b95._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 11""" + date="2020-01-01T18:54:04Z" + content=""" +Generally if git-annex unused does not identify some object as unused, that +you expected would be unused, it's because it found a branch that still +uses that object. It might be some old branch (or tag) that you made and +forgot about, it might be a remote tracking branch, either for a remote +that you forgot to sync the changes to, or for an old remote that +got removed but in a way that left the tracking branch around. +annex.used-refspec can also pull in other, non-branch refs. +"""]] diff --git a/doc/todo/git-annex-cat/comment_4_8708bf0aef0025e2ed1a8b9d2a7f0112._comment b/doc/todo/git-annex-cat/comment_4_8708bf0aef0025e2ed1a8b9d2a7f0112._comment new file mode 100644 index 0000000000..7c602eb537 --- /dev/null +++ b/doc/todo/git-annex-cat/comment_4_8708bf0aef0025e2ed1a8b9d2a7f0112._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2020-01-01T18:44:37Z" + content=""" +@Ilya_Shlyakhter, I'd assume: + +* some remotes would write to the named pipe +* some remotes would overwrite it with a file +* some remotes would open it, try to seek around as they do non-sequential + recieves, and hang or something +* some remotes would maybe open and write to it, but would no longer be + able to resume interrupted transfers, since they would I guess see its + size as 0 +"""]]