* The first git commit legitimately has no parents. Avoid recentchanges

spewing uninitialised value warnings and debug messages about it.
  Dummying up a parent of 0000000 allows gitweb to work too.
master
Joey Hess 2007-11-12 12:53:46 -05:00
parent 3c3135c6a8
commit 8ffa59e610
2 changed files with 11 additions and 4 deletions

View File

@ -196,10 +196,14 @@ sub _parse_diff_tree ($@) { #{{{
}
}
debug("No 'tree' or 'parents' seen in diff-tree output")
if !defined $ci{'tree'} || !defined $ci{'parents'};
debug("No 'tree' seen in diff-tree output") if !defined $ci{'tree'};
$ci{'parent'} = @{ $ci{'parents'} }[0] if defined $ci{'parents'};
if (defined $ci{'parents'}) {
$ci{'parent'} = @{ $ci{'parents'} }[0];
}
else {
$ci{'parent'} = 0 x 40;
}
# Commit message.
while (my $line = shift @{ $dt_ref }) {

5
debian/changelog vendored
View File

@ -28,8 +28,11 @@ ikiwiki (2.12) UNRELEASED; urgency=low
It needs to be setgid if the master repo is a shared repository, so
that pushes into the working copy repository happen as the same group,
avoiding permissions problems.
* The first git commit legitimately has no parents. Avoid recentchanges
spewing uninitialised value warnings and debug messages about it.
Dummying up a parent of 0000000 allows gitweb to work too.
-- Joey Hess <joeyh@debian.org> Mon, 12 Nov 2007 12:26:45 -0500
-- Joey Hess <joeyh@debian.org> Mon, 12 Nov 2007 12:48:55 -0500
ikiwiki (2.11) unstable; urgency=low