Package: git
Version: 1:2.0~next.20140117-1
Severity: wishlist
Tags: upstream
Corrupting a repository sometimes makes it essentially invisible as
far as commands like "git rev-parse --git-dir" care, for example if
the refs/ subdir of a .git dir was removed. Worse, git doesn't
diagnose the problem except by saying it couldn't find a git
repository.
Potential fixes:
1. A new command 'git rev-parse --why-u-no-git-dir <path>'
(or an option to fsck?) could try each test for a git repository
in turn and figure out which ones failed.
2. Code that looks for a git repository could warn when it both
(a) failed to find a git repository and (b) found something that
was almost a git repository and then automatically use the code
from (1) to help the caller diagnose the problem.
Noticed by Cristian Ciupitu during the conversation surrounding
http://colabti.org/irclogger/irclogger_log/git?date=2014-01-25#l96
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
