Re: What's cooking in git.git (Jan 2012, #08; Tue, 31)

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 1, 2012, 20:37 UTC
Message-ID: <7v39au47dt.fsf@alter.siamese.dyndns.org>
In-Reply-To: <m3fweudaf6.fsf@localhost.localdomain>

Jakub Narebski <jnareb@gmail.com> writes:

Show 11 quoted lines

> Hmmm... strange.  I have applied my patches on top of earlier version
> of project_filter commits:
>
>    - gitweb: Make project search respect project_filter
>    - gitweb: Improve projects search form
>    - gitweb: place links to parent directories in page header
>    - gitweb: add project_filter to limit project list to a subdirectory
>
> and all gitweb tests passes.
>
> I will investigate.

I am getting

    7ad1b64084ff003f71fe749a3e5a74d071a193d8 is the first bad commit
    commit 7ad1b64084ff003f71fe749a3e5a74d071a193d8
    Author: Bernhard R. Link <brl+git@mail.brlink.eu>
    Date:   Mon Jan 30 21:05:47 2012 +0100

        gitweb: move hard coded .git suffix out of git_get_projects_list

*** t9502-gitweb-standalone-parse-output.sh *** ok 1 - setup ok 2 - snapshot: full sha1 ok 3 - snapshot: shortened sha1 ok 4 - snapshot: almost full sha1 ok 5 - snapshot: HEAD ok 6 - snapshot: short branch name (master) ok 7 - snapshot: short tag name (first) ok 8 - snapshot: full branch name (refs/heads/master) ok 9 - snapshot: full tag name (refs/tags/first) ok 10 - snapshot: hierarchical branch name (xx/test) ok 11 - forks: setup ok 12 - forks: not skipped unless "forks" feature enabled ok 13 - forks: forks skipped if "forks" feature enabled not ok - 14 forks: "forks" action for forked repository # # gitweb_run "p=foo.git;a=forks" && # grep -q ">foo/foo-forked\\.git<" gitweb.body && # grep -q ">fork of foo<" gitweb.body # ok 15 - forks: can access forked repository ok 16 - forks: project_index lists all projects (incl. forks) # failed 1 among 16 test(s)

The output file gitweb.body has this in it:

<div class="page_body"> <br /><br /> 404 - No forks found <br /> </div> <div class="page_footer">