summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar Mark Lodato <lodatom@gmail.com>2010-12-18 00:38:38 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2010-12-18 22:58:40 -0800
commit0c806a06a311081ba02f60ffd2711853c1b9d6fc (patch)
tree307e98b5904d4038f9e11505da90f33f104a5d4a /Documentation
parentuserdiff: fix typo in ruby and python word regexes (diff)
downloadtgif-0c806a06a311081ba02f60ffd2711853c1b9d6fc.tar.xz
fsck docs: remove outdated and useless diagnostic
In git-fsck(1), there was a reference to the warning "<tree> has full pathnames in it". This exact wording has not been used since 2005 (commit f1f0d0889e55), when the wording was changed slightly. More importantly, the description of that warning was useless, and there were many other similar warning messages which were not document at all. Since all these warnings are fairly obvious, there is no need for them to be in the man page. Signed-off-by: Mark Lodato <lodatom@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/git-fsck.txt3
1 files changed, 0 insertions, 3 deletions
diff --git a/Documentation/git-fsck.txt b/Documentation/git-fsck.txt
index 3ad48a6336..86f9b2bf91 100644
--- a/Documentation/git-fsck.txt
+++ b/Documentation/git-fsck.txt
@@ -123,9 +123,6 @@ dangling <type> <object>::
The <type> object <object>, is present in the database but never
'directly' used. A dangling commit could be a root node.
-warning: git-fsck: tree <tree> has full pathnames in it::
- And it shouldn't...
-
sha1 mismatch <object>::
The database has an object who's sha1 doesn't match the
database value.