mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comments

Browse source
This commit is contained in:
Joey Hess 2020-01-01 15:03:01 -04:00
parent a234ad7368
commit bc70a8b3f6
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 28 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
doc/git-annex-unused/comment_11_5c1ea2e8ac475d8c0ddca2c38f968b95._comment Normal file
View file

@ -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.
"""]]

15
doc/todo/git-annex-cat/comment_4_8708bf0aef0025e2ed1a8b9d2a7f0112._comment Normal file
View file

@ -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
"""]]