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

respond and close

Browse source
This commit is contained in:
Joey Hess 2020-03-02 14:58:31 -04:00
parent 701f8cb00b
commit 1a8087ace5
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 14 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
doc/bugs/git-annex-fsck_reports_dead_keys_as_errors.mdwn
View file

@ -51,3 +51,4 @@ git-annex: fsck: 1 failed
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
git-annex helps me keep my sanity :)
> [[notabug|done]] per comments --[[Joey]]

13
doc/bugs/git-annex-fsck_reports_dead_keys_as_errors/comment_4_c5f902c1c5fdb1011577b9d5edde6b45._comment Normal file
View file

@ -0,0 +1,13 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2020-03-02T18:54:05Z"
content="""
As yes, I missed that you also had an example of fsck --key as well as fsck
of a file in the working tree with a dead key.
I think the same basic reasoning applies for fsck --key as for fscking a
worktree file. The user appears to be particularly interested in that key,
so fsck should tell them about the obious problem that it has no remaining
content. It's not like --all.
"""]]