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

closing

Browse source
This commit is contained in:
Joey Hess 2021-06-30 11:43:39 -04:00
parent 0e7906e802
commit 73ccf34763
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 21 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/Git_repos_corrupt_themselves.mdwn
View file

@ -104,3 +104,5 @@ Git fsck spat out a huge list of broken blobs and trees.
### 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)
There are a surprising amount of weird bugs and quirks like these but it's such an amazing tool, there's nothing like it.
> [[fixed|done]] --[[Joey]]

17
doc/bugs/Git_repos_corrupt_themselves/comment_18_238bbbcabd626c33acc14f930a7d536c._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 18"""
date="2021-06-30T15:36:39Z"
content="""
If the assistant crashed in the middle of a repair that confirms my
analysis, and my fix will avoid both the data loss problem *and* the crash.
Only remaining question to me is why would it trigger an unncessary repair.
But that could be anything that causes git fsck to exit nonzero. Or it
might be that git fsck found an actual problem, but not one that was
preventing the repo from working. Eg, a missing/corrupt object used
somewhere deep in the history.
(Note that git-repair already exists. git-annex integrates it.)
"""]]