git-repair - [no description]

	Commit message (Collapse)	Author	Age
*	urgle	Joey Hess	2013-11-20
\|
*	try to recover even if git fsck cannot be coaxed to tell us any bad objects	Joey Hess	2013-11-20
\| \| \| \| \| \| \|	Sometimes git fsck outputs no shas even with --verbose, but fails, due to badly corrupt objects. The best thing to do in this situation is to try to pull and rsync from remotes, hoping that the bad objects will be overwritten.
*	oops	Joey Hess	2013-11-20
\|
*	merge from git-annex	Joey Hess	2013-11-20
\|
*	Write a dummy .git/HEAD if the file is missing, as git otherwise will not ↵	Joey Hess	2013-11-20
\| \| \| \|	treat the repository as a git repo.
*	whoops	Joey Hess	2013-11-19
\|
*	retrying	Joey Hess	2013-11-19
\|
*	initial work on git repository destroyer	Joey Hess	2013-11-19
\| \| \| \| \|	I suspect this might sometimes corrupt the source repo, so use with caution!
*	copied from git-annex	Joey Hess	2013-11-18