| commit | cb2cada6da9d71604fd09efbff47cddbea453e1e | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 29 Apr 2007 00:29:23 +0000 (28 20:29 -0400) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Sun, 29 Apr 2007 01:06:00 +0000 (28 18:06 -0700) | ||
| tree | a8801dad29e38ee20ee6d477d64e27321bc24c0a | treesnapshot (tar.gz zip) |
| parent | 26e60160a074747fbe8866ddac4e0c7660c17ff6 | commitdiff |
Catch empty pathnames in trees during fsck
Released versions of fast-import have been able to create a tree that
contains files or subtrees that contain no name. Unfortunately these
trees aren't valid, but people may have actually tried to create them
due to bugs in import-tars.perl or their own fast-import frontend.
We now look for this unusual condition and warn the user if at
least one of their tree objects contains the problem.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Released versions of fast-import have been able to create a tree that
contains files or subtrees that contain no name. Unfortunately these
trees aren't valid, but people may have actually tried to create them
due to bugs in import-tars.perl or their own fast-import frontend.
We now look for this unusual condition and warn the user if at
least one of their tree objects contains the problem.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
| builtin-fsck.c | diffblobblamehistory |