gitweb: Use single implementation of export_ok check.

GitWeb source contains a special function that implements the
export_ok check, but validate_project still uses a separate copy
of essentially the same code.

This patch makes it use the dedicated function, thus ensuring
that all checks are done through a single code path.

Signed-off-by: Alexander Gavrilov <redacted>
Acked-by: Jakub Narebski <redacted>
Signed-off-by: Junio C Hamano <redacted>

diff --git a/gitweb.perl b/gitweb.perl
index 8db5c344b10a643180b99129a0203ec3261accf548f6a1433f89fd6ee0cc694c..fefa8f94e09ca5f387a5ae766d0ccc5512338b647a2e7b67e100c1d9809d0f92 100755 (executable)
--- a/gitweb.perl
+++ b/gitweb.perl
@@ -914,8 +914,7 @@ sub validate_project {
        my $input = shift || return undef;
        if (!validate_pathname($input) ||
                !(-d "$projectroot/$input") ||
        my $input = shift || return undef;
        if (!validate_pathname($input) ||
                !(-d "$projectroot/$input") ||

-               !check_head_link("$projectroot/$input") ||
-               ($export_ok && !(-e "$projectroot/$input/$export_ok")) ||
+               !check_export_ok("$projectroot/$input") ||

                ($strict_export && !project_in_list($input))) {
                return undef;
        } else {
                ($strict_export && !project_in_list($input))) {
                return undef;
        } else {