git-repair - [no description]

	Commit message (Collapse)	Author	Age
...
\| *	Support old git versions from before git fsck --no-dangling was implemented.	Joey Hess	2014-01-13
\| \|
\| *	prep release1.20131213	Joey Hess	2013-12-13
\| \|
\| *	merge from git-annex	Joey Hess	2013-12-10
\| \|
\| *	prep release	Joey Hess	2013-12-03
\| \|
\| *	Fix build deps. Closes: #731179	Joey Hess	2013-12-03
\| \|
\| *	update descs	Joey Hess	2013-11-22
\| \|
\| *	releasing package git-repair version 1.201311221.20131122	Joey Hess	2013-11-22
\| \|
\| *	clean up	Joey Hess	2013-11-21
\| \|
\| *	improve findMissing	Joey Hess	2013-11-21
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	git cat-file -p cannot be relied on to tell when an object is corrupt. If it fails, the fsck may not find all bad objects -- but as long as fsck exits nonzero, it will return a failing fsckresult, and so recovery will run. In recovery, the objects get unpacked. This allows the improved findMissing to find all corrupt loose objects when fsck is run again as part of the recovery. Removed the repack / prune-packed workaround that I added earlier to find corrupt loose objects that fsck wasn't finding. That was slow, and we want to keep all loose objects, so that findMissing will work. And, it's unncessary, now that findMissing is fixed. Also, fixed some places where unreadable files would crash recovery.
\| *	combine test program into git-repair	Joey Hess	2013-11-21
\| \|
\| *	more 0s	Joey Hess	2013-11-21
\| \|
\| *	remove fsck tryharder code	Joey Hess	2013-11-20
\| \| \| \| \| \| \| \| \| \| \| \|	It turned out to be broken, and led to failures. 6d67245728bbbc07ad1eeaf5b3c49f64c6bbcd11 was a better fix for the problem that code tried to fix.
\| *	update	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.
\| *	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.
\| *	changelog	Joey Hess	2013-11-19
\| \|
\| *	use optparse-applicative	Joey Hess	2013-11-18
\| \|
\| *	debianization	Joey Hess	2013-11-18
\|
*	finalise changelog for 1.20151215-2 uploaddebian/1.20151215-2 archive/debian/1.20151215-2	Sean Whitton	2020-01-01
\|
*	standardise & update d/copyright	Sean Whitton	2020-01-01
\|
*	Rules-Requires-Root: no	Sean Whitton	2020-01-01
\|
*	Drop debian/gbp.conf	Sean Whitton	2020-01-01
\|
*	std-ver 4.4.1	Sean Whitton	2020-01-01
\|
*	adopt package & use https in URIs	Sean Whitton	2020-01-01
\|
*	Commit Debian 3.0 (quilt) metadatadebian/1.20151215-1.2 archive/debian/1.20151215-1.2	Sean Whitton	2018-07-22
\| \| \| \|	[dgit (5.10~bpo9+1) quilt-fixup]
*	changelog for NMU	Sean Whitton	2018-07-22
\|
*	Commit Debian 3.0 (quilt) metadatadebian/1.20151215-1.1 archive/debian/1.20151215-1.1	Sean Whitton	2017-07-25
\| \| \| \|	[dgit (3.12) quilt-fixup]
*	changelog for NMU	Sean Whitton	2017-07-25
\|
*	git-repair (1.20151215-1) unstable; urgency=medium	Richard Hartmann	2015-12-15
\| \| \| \| \| \|	* Package 1.20151215-1 [dgit import unpatched git-repair 1.20151215-1]
*	Import git-repair_1.20151215.orig.tar.xz	Joey Hess	2015-12-15
	[dgit import orig git-repair_1.20151215.orig.tar.xz]