git/gitweb, branch v1.8.2.2

gitweb/INSTALL: Simplify description of GITWEB_CONFIG_SYSTEM

2013-04-15T14:25:46Z

The flow of the text describing GITWEB_CONFIG_SYSTEM and GITWEB_CONFIG_COMMON in gitweb/INSTALL is awkward. "This is bad. Oh the other hand, better is broken. Therefore we do this." forces readers to make multiple guesses while reading: "ok, bad, so you plan to change it and warn us about upcoming change? oh, not that, changing it is bad, so we have to live with it? oh, not that, there is another one that is common and that is what we can use". Better rewrite said paragraph to avoid such a mental roller-coaster in the first place. Signed-off-by: Junio Hamano Signed-off-by: Jakub Narebski Signed-off-by: Junio C Hamano

Correct common spelling mistakes in comments and tests

2013-04-12T20:38:40Z

Most of these were found using Lucas De Marchi's codespell tool. Signed-off-by: Stefano Lattarini Signed-off-by: Jonathan Nieder Acked-by: Matthieu Moy Signed-off-by: Junio C Hamano

doc: various spelling fixes

2013-04-12T19:00:52Z

Most of these were found using Lucas De Marchi's codespell tool. Signed-off-by: Stefano Lattarini Signed-off-by: Jonathan Nieder Signed-off-by: Junio C Hamano

gitweb/README: remove reference to git.kernel.org

2013-03-07T19:38:33Z

git.kernel.org no longer uses gitweb but has switched to cgit. Info about this can be found on: https://www.kernel.org/pelican.html or simply by looking at http://git.kernel.org . This is change since 2013-03-01. Signed-off-by: Fredrik Gustafsson Signed-off-by: Junio C Hamano

gitweb: refer to picon/gravatar images over the same scheme

2013-01-29T02:58:50Z

With the current code, the images from picon and gravatar are requested over http://, and browsers give mixed contents warning when gitweb is served over https://. Just drop the scheme: part from the URL, so that these external sites are accessed over https:// in such a case. Signed-off-by: Andrej E Baranov Signed-off-by: Junio C Hamano

Merge branch 'os/gitweb-highlight-uncaptured' into maint

2013-01-12T00:48:30Z

"gitweb", when sorting by age to show repositories with new activities first, used to sort repositories with absolutely nothing in it early, which was not very useful. * os/gitweb-highlight-uncaptured: gitweb: fix error in sanitize when highlight is enabled

Merge branch 'md/gitweb-sort-by-age' into maint

2013-01-10T22:04:21Z

* md/gitweb-sort-by-age: gitweb: Sort projects with undefined ages last

gitweb: fix error in sanitize when highlight is enabled

2013-01-02T00:27:27Z

$1 becomes undef by internal regex, since it has no capture groups. Match against accpetable control characters using index() instead of a regex. Signed-off-by: Orgad Shaneh Signed-off-by: Junio C Hamano

gitweb: Sort projects with undefined ages last

2012-12-11T18:08:00Z

Sorting gitweb's project list by age ('Last Change') currently shows projects with undefined ages at the head of the list. This gives a less useful result when there are a number of projects that are missing or otherwise faulty and one is trying to see what projects have been updated recently. Fix by sorting these projects with undefined ages at the bottom of the list when sorting by age. Signed-off-by: Matthew Daley Signed-off-by: Junio C Hamano

Merge branch 'pp/gitweb-config-underscore'

2012-11-29T20:52:17Z

The key "gitweb.remote_heads" is not legal git config; this maps it to "gitweb.remoteheads". * pp/gitweb-config-underscore: gitweb: make remote_heads config setting work