Gitweb; ordering of fork list on summary page (was Vanilla gitweb vs repo.or.cz)

From: Mike Ralphson <mike.ralphson@gmail.com>
Date: Jul 23, 2008, 17:10 UTC
Message-ID: <e2b179460807231010m44ff446auc054ead9178c711b@mail.gmail.com>

2008/7/13 Petr Baudis <pasky@suse.cz>:

>  Then, there is the http://repo.or.cz/w/git/gitweb.git repository,
> which was my old attempt at maintaining gitweb actively. Unfortunately,
> this didn't quite work out because of my general lack of time and
> dedication.

Notwithstanding the above, I've pushed a little 'fix' to the mob branch:

http://repo.or.cz/w/git/gitweb.git?a=commitdiff;h=3e8f6e9125071a7e17c88efb69c1780d775025bc

The list of forks on the summary page was unsorted, this just makes them sorted by age, which seems a fair way to decide which forks are shown before the list size cut-off (15) kicks in.

s/noheader/no_header was just to make it obvious what the parameter affects, so all the code can be found with one grep, and s/undef/'age' just shows the intent, although that parameter isn't what actually controls the sort order. Or, I guess, the sorting could be refactored out of the header generation code.

Mike