From: Jakub Narebski <hidden> Date: 2016-06-15 22:47:57
This is resend of early part of "[PATCH 0/6] Gitweb caching changes v2"
thread by John 'Warthog9' Hawley (J.H.),
Message-ID: [off-list ref]
http://thread.gmane.org/gmane.comp.version-control.git/135052
or alternatively
git://git.kernel.org/pub/scm/git/warthog9/gitweb.git gitweb-ml-v2
with a few modifications of my own. Those patches were send originally as
responses in the mentioned thread, for further comments from original
author. As the discussion didn't pick up (because of kernel.org upgrade, and
perhaps due to end-of-year stuff), I am resending those patches in a
separate thread for a better visibility; only comments are changed.
This series of patches is rebased on top of commit 37bae10
(Merge branch 'maint', 2009-12-31) in 'master' branch.
Change that apply to all patches in series:
* moving from "GITWEB - " to "gitweb: " as subsystem prefix
* changing author to John 'Warthog9' Hawley [off-list ref]
(it was John 'Warthog9' Hawley [off-list ref])
* add signoff or change it to John 'Warthog9' Hawley [off-list ref],
and of course add my own signoff.
I have included reply to neither "GITWEB - File based caching layer"
nor "GITWEB - Separate defaults from main file" in this thread/series.
I haven't included the main point of the whole series, namely adding
response caching layer in the form that is used in git.kernel.org, because
I think this patch should be split into smaller parts, and unit-tested.
As it is now it is a bit of mess. I have done patch which makes gitweb
always use explicit filehandle when printing (simplifying a bit it
replaces 'print <something>' by 'print {$out} <something>', with $out set
to \*STDOUT), as a patch that prepares for (optional) gitweb caching, while
not affecting throughput, latency and memory consumption when caching is
disabled, as opposed to original solution by J.H. of always storing whole
response in scalar and writing it at the end.
I haven't included splitting of gitweb_defaults.perl off gitweb.perl, as it
was after large and invasive gitweb caching patch, it would require
substantial changes to gitweb tests upfront (by testing built gitweb.cgi and
not source gitweb.perl), and needs fixing of Makefile to actually work
reliably (we could have to process both gitweb.perl and
gitweb_defaults.perl, while provided Makefile process only the file which
triggered the rule... I think).
I am not sure if 'gitweb: Add option to force version match' is a good
solution to the problem it tires to address, i.e. if it is worth having,
and I am not sure if I did 'gitweb: Makefile improvements' correctly.
John 'Warthog9' Hawley (4):
gitweb: Load checking
gitweb: Add option to force version match
gitweb: Optionally add "git" links in project list page
gitweb: Makefile improvements
Makefile | 65 +++++---------------------
gitweb/Makefile | 129 ++++++++++++++++++++++++++++++++++++++++++++++++++++
gitweb/README | 14 +++++-
gitweb/gitweb.perl | 80 ++++++++++++++++++++++++++++++--
4 files changed, 230 insertions(+), 58 deletions(-)
create mode 100644 gitweb/Makefile
John, any comments?
--
Jakub Narebski
ShadeHawk or jnareb on #git
Poland
From: Jakub Narebski <hidden> Date: 2016-06-15 22:47:57
From: John 'Warthog9' Hawley <warthog9@kernel.org>
This adds $git_versions_must_match variable, which is set to true
value checks that we are running on the same version of git that we
shipped with, and if not throw '500 Internal Server Error' error.
What is checked is the version of gitweb (embedded in building
gitweb.cgi), against version of runtime git binary used.
Gitweb can usually run with a mismatched git install. This is more
here to give an obvious warning as to whats going on vs. silently
failing.
By default this feature is turned off.
Signed-off-by: John 'Warthog9' Hawley <warthog9@kernel.org>
Signed-off-by: Jakub Narebski <redacted>
---
I don't quite see the reason behind such option, and I think that
error (instead of for example warning) on version mismatch is too much.
In short: this change is meant to avoid situation where version
mismatch results in silent error, but it would work only if it would
be default on; on the other hand having it default on is I think too
inconvenient, so I changed it to default off, which perhaps defeats
the stated purpose of this patch.
This is an RFC because formatting of error page is a bit rough, and
(ab)uses exist CSS classes instead of creating new classnames for
semantic markup.
Differences from original version, by J.H.:
* Changed name and flipped meaning of config variable, from
$missmatch_git to $git_versions_must_match
* $git_versions_must_match is boolean flag - do not compare with an
empty string.
* Changed error message a bit, fixed style, added entry in README
gitweb/README | 3 +++
gitweb/gitweb.perl | 33 +++++++++++++++++++++++++++++++++
2 files changed, 36 insertions(+), 0 deletions(-)
@@ -233,6 +233,9 @@ not include variables usually directly set during build): If server load exceed this value then return "503 Service Unavailable" error. Server load is taken to be 0 if gitweb cannot determine its value. Set it to undefined value to turn it off. The default is 300.+ * $git_versions_must_match+ If set, gitweb fails with 500 Internal Server Error if the version of gitweb+ doesn't match version of git binary. The default is false. Projects list file format
@@ -221,6 +221,9 @@ our %avatar_size = ('double'=>32);+# If it is true, exit if gitweb version and git binary version don't match+our$git_versions_must_match=0;+# Used to set the maximum load that we will still respond to gitweb queries.# If server load exceed this value then return "503 server busy" error.# If gitweb cannot determined server load, it is taken to be 0.
@@ -581,6 +584,36 @@ if (defined $maxload && get_loadavg() > $maxload) {our$git_version=qx("$GIT" --version)=~m/git version (.*)$/?$1:"unknown";$number_of_git_cmds++;+# Throw an error if git versions does not match, if $git_versions_must_match is true.+if($git_versions_must_match&&+$git_versionne$version){+git_header_html('500 - Internal Server Error');+my$admin_contact=+defined$ENV{'SERVER_ADMIN'}?", $ENV{'SERVER_ADMIN'},":'';+print<<"EOT";+<divclass="page_body">+<br/><br />+500-InternalServerError+<br/>+</div>+<hr/>+<divclass="readme">+<h1align="center">***Warning***</h1>+<p>+Thisversionofgitwebwascompiledfor<b>@{[esc_html($version)]}</b>,+howevergitversion<b>@{[esc_html($git_version)]}</b>wasfoundonserver,+andadministratorrequestedstrictversionchecking.+</p>+<p>+Pleasecontacttheserveradministrator${admin_contact}toeitherconfigure+gitwebtoallowmismatchedversions,orupdategitorgitwebinstallation.+</p>+</div>+EOT+git_footer_html();+exit;+}+$projects_list||=$projectroot;# ======================================================================
From: Jakub Narebski <hidden> Date: 2016-06-15 22:47:57
From: John 'Warthog9' Hawley <warthog9@kernel.org>
This commit adjust the main Makefile so you can simply run
make gitweb
which in turn calls gitweb/Makefile. This means that in order to
generate gitweb, you can simply run 'make' from gitweb subdirectory:
cd gitweb
make
Targets gitweb/gitweb.cgi and (dependent on JSMIN being defined)
gitweb/gitweb.min.js in main Makefile are preserved for backward
compatibility.
Signed-off-by: John 'Warthog9' Hawley <warthog9@kernel.org>
Signed-off-by: Jakub Narebski <redacted>
---
This implements separate Makefile for gitweb, with main Makefile calling
it, like for gitk-git/, git-gui/, Documentation/, t/, and templates/
directories. The original patch by J.H. did it the opposite way, with
gitweb/Makefile calling main Makefile.
It is marked as RFC because I don't feel that my make-fu is strong enough
to be sure that there are no errors / mistakes. Very slightly tested.
Makefile | 65 +++++----------------------
gitweb/Makefile | 129 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 141 insertions(+), 53 deletions(-)
create mode 100644 gitweb/Makefile
@@ -282,29 +282,6 @@ pathsep = :# JavaScript minifier invocation that can function as filterJSMIN=-# default configuration for gitweb-GITWEB_CONFIG=gitweb_config.perl-GITWEB_CONFIG_SYSTEM=/etc/gitweb.conf-GITWEB_HOME_LINK_STR=projects-GITWEB_SITENAME=-GITWEB_PROJECTROOT=/pub/git-GITWEB_PROJECT_MAXDEPTH=2007-GITWEB_EXPORT_OK=-GITWEB_STRICT_EXPORT=-GITWEB_BASE_URL=-GITWEB_LIST=-GITWEB_HOMETEXT=indextext.html-GITWEB_CSS=gitweb.css-GITWEB_LOGO=git-logo.png-GITWEB_FAVICON=git-favicon.png-ifdef JSMIN-GITWEB_JS=gitweb.min.js-else-GITWEB_JS=gitweb.js-endif-GITWEB_SITE_HEADER=-GITWEB_SITE_FOOTER=-exportprefixbindirsharedirsysconfdirCC=gcc
@@ -0,0 +1,129 @@+# The default target of this Makefile is...+all::++# Define V=1 to have a more verbose compile.+#+# Define JSMIN to point to JavaScript minifier that functions as+# a filter to have gitweb.js minified.+#++prefix?=$(HOME)+bindir?=$(prefix)/bin+RM?=rm-f++# JavaScript minifier invocation that can function as filter+JSMIN?=++# default configuration for gitweb+GITWEB_CONFIG=gitweb_config.perl+GITWEB_CONFIG_SYSTEM=/etc/gitweb.conf+GITWEB_HOME_LINK_STR=projects+GITWEB_SITENAME=+GITWEB_PROJECTROOT=/pub/git+GITWEB_PROJECT_MAXDEPTH=2007+GITWEB_EXPORT_OK=+GITWEB_STRICT_EXPORT=+GITWEB_BASE_URL=+GITWEB_LIST=+GITWEB_HOMETEXT=indextext.html+GITWEB_CSS=gitweb.css+GITWEB_LOGO=git-logo.png+GITWEB_FAVICON=git-favicon.png+ifdef JSMIN+GITWEB_JS=gitweb.min.js+else+GITWEB_JS=gitweb.js+endif+GITWEB_SITE_HEADER=+GITWEB_SITE_FOOTER=++# include user config+-include ../config.mak.autogen+-include ../config.mak++# determine version+../GIT-VERSION-FILE:.FORCE-GIT-VERSION-FILE+$(QUIET_SUBDIR0)../$(QUIET_SUBDIR1)GIT-VERSION-FILE++-include ../GIT-VERSION-FILE++### Build rules++SHELL_PATH?=$(SHELL)+PERL_PATH?=/usr/bin/perl++# Shell quote;+bindir_SQ=$(subst','\'',$(bindir)) #'+SHELL_PATH_SQ=$(subst','\'',$(SHELL_PATH)) #'+PERL_PATH_SQ=$(subst','\'',$(PERL_PATH)) #'++# Quiet generation (unless V=1)+QUIET_SUBDIR0=+$(MAKE)-C# space to separate -C and subdir+QUIET_SUBDIR1=++ifneq ($(findstring $(MAKEFLAGS),w),w)+PRINT_DIR=--no-print-directory+else # "make -w"+NO_SUBDIR=:+endif++ifneq ($(findstring $(MAKEFLAGS),s),s)+ifndef V+QUIET=@+QUIET_GEN=$(QUIET)echo' 'GEN$@;+QUIET_SUBDIR0=+@subdir=+QUIET_SUBDIR1=;$(NO_SUBDIR)echo' 'SUBDIR$$subdir;\+$(MAKE)$(PRINT_DIR)-C$$subdir+exportV+exportQUIET+exportQUIET_GEN+exportQUIET_SUBDIR0+exportQUIET_SUBDIR1+endif+endif++all::gitweb.cgi++ifdef JSMIN+FILES=gitweb.cgigitweb.min.js+gitweb.cgi:gitweb.perlgitweb.min.js+else # !JSMIN+FILES=gitweb.cgi+gitweb.cgi:gitweb.perl+endif # JSMIN++gitweb.cgi:+$(QUIET_GEN)$(RM)$@$@+&&\+sed-e'1s|#!.*perl|#!$(PERL_PATH_SQ)|'\+-e's|++GIT_VERSION++|$(GIT_VERSION)|g'\+-e's|++GIT_BINDIR++|$(bindir)|g'\+-e's|++GITWEB_CONFIG++|$(GITWEB_CONFIG)|g'\+-e's|++GITWEB_CONFIG_SYSTEM++|$(GITWEB_CONFIG_SYSTEM)|g'\+-e's|++GITWEB_HOME_LINK_STR++|$(GITWEB_HOME_LINK_STR)|g'\+-e's|++GITWEB_SITENAME++|$(GITWEB_SITENAME)|g'\+-e's|++GITWEB_PROJECTROOT++|$(GITWEB_PROJECTROOT)|g'\+-e's|"++GITWEB_PROJECT_MAXDEPTH++"|$(GITWEB_PROJECT_MAXDEPTH)|g'\+-e's|++GITWEB_EXPORT_OK++|$(GITWEB_EXPORT_OK)|g'\+-e's|++GITWEB_STRICT_EXPORT++|$(GITWEB_STRICT_EXPORT)|g'\+-e's|++GITWEB_BASE_URL++|$(GITWEB_BASE_URL)|g'\+-e's|++GITWEB_LIST++|$(GITWEB_LIST)|g'\+-e's|++GITWEB_HOMETEXT++|$(GITWEB_HOMETEXT)|g'\+-e's|++GITWEB_CSS++|$(GITWEB_CSS)|g'\+-e's|++GITWEB_LOGO++|$(GITWEB_LOGO)|g'\+-e's|++GITWEB_FAVICON++|$(GITWEB_FAVICON)|g'\+-e's|++GITWEB_JS++|$(GITWEB_JS)|g'\+-e's|++GITWEB_SITE_HEADER++|$(GITWEB_SITE_HEADER)|g'\+-e's|++GITWEB_SITE_FOOTER++|$(GITWEB_SITE_FOOTER)|g'\+$<>$@+&&\+chmod+x$@+&&\+mv$@+$@++ifdef JSMIN+gitweb.min.js:gitweb.js+$(QUIET_GEN)$(JSMIN)<$<>$@+endif # JSMIN++clean:+$(RM)$(FILES)++.PHONY:allclean .FORCE-GIT-VERSION-FILE
From: Jakub Narebski <hidden> Date: 2016-06-15 22:47:57
From: John 'Warthog9' Hawley <warthog9@kernel.org>
This adds a "git" link for each project in the project list page,
should a common $gitlinkurl_base be defined and not empty. The full
URL of each link is composed of $gitlinkurl_base and project name.
It is intended for git:// links, and in fact GITWEB_BASE_URL build
variable is used as its default value only if it starts with git://
This does make the assumption that the git repositories share a common
path. Nothing to date is known to actually make use of introduced
link.
Created "git" link follows rel=vcs-* microformat specification:
http://kitenet.net/~joey/rfc/rel-vcs/
Signed-off-by: John 'Warthog9' Hawley <warthog9@kernel.org>
Signed-off-by: Jakub Narebski <redacted>
---
I think it might be good idea... but for the fact "Nothing to date is
known to actually make use of introduced link". What's its intended
use?
Differences to original version by John 'Warthog9' Hawley (J.H.):
* It doesn't cause syntax error ;-)
* Escaping of attribute value is left to CGI.pm (avoid double escaping)
* $gitlinkurl got renamed to $gitlinkurl_base, now includes git://
prefix, and defaults to GITWEB_BASE_URL if it begins with git://
* Added description of $gitlinkurl_base to gitweb/README
* Uses rel=vcs-* microformat by Joey Hess
I assume that nobody sane would define $gitlinkurl_base to "0";
the code assumes that is enough to check that $gitlinkurl_base
is true-ish.
gitweb/README | 4 ++++
gitweb/gitweb.perl | 8 ++++++++
2 files changed, 12 insertions(+), 0 deletions(-)
@@ -71,6 +71,7 @@ You can specify the following configuration variables when building GIT: * GITWEB_BASE_URL Git base URLs used for URL to where fetch project from, i.e. full URL is "$git_base_url/$project". Shown on projects summary page.+ If it begins with "git://" it is also used for $gitlinkurl_base, see below. Repository URL for project can be also configured per repository; this takes precedence over URLs composed from base URL and a project name. Note that you can setup multiple base URLs (for example one for
@@ -204,6 +205,9 @@ not include variables usually directly set during build): access, and one for http:// "dumb" protocol access). Note that per repository configuration in 'cloneurl' file, or as values of gitweb.url project config.+ * $gitlinkurl_base+ Git base URL used (if it is defined and not empty) for "git" link in+ projects list, for each project. Full URL is "$gitlinkurl_base/$project". * $default_blob_plain_mimetype Default mimetype for blob_plain (raw) view, if mimetype checking doesn't result in some other type; by default 'text/plain'.
@@ -224,6 +224,10 @@ our %avatar_size = (# If it is true, exit if gitweb version and git binary version don't matchour$git_versions_must_match=0;+# If this variable is set and not empty, add an extra link called "git"+# for each project in project list. Full URL is "$gitlinkurl_base/$project".+our$gitlinkurl_base=("++GITWEB_BASE_URL++"=~m!^(git://.*)$!)?$1:'';+# Used to set the maximum load that we will still respond to gitweb queries.# If server load exceed this value then return "503 server busy" error.# If gitweb cannot determined server load, it is taken to be 0.
From: Jakub Narebski <hidden> Date: 2016-06-15 22:47:57
From: John 'Warthog9' Hawley <warthog9@kernel.org>
This changes slightly the behavior of gitweb, so that it verifies
that the box isn't inundated with before attempting to serve gitweb.
If the box is overloaded, it basically returns a 503 Server Unavailable
until the load falls below the defined threshold. This helps dramatically
if you have a box that's I/O bound, reaches a certain load and you
don't want gitweb, the I/O hog that it is, increasing the pain the
server is already undergoing.
This behavior is controlled by $maxload configuration variable.
Default is a load of 300, which for most cases should never be hit.
Unset it (set it to undefined value, i.e. undef) to turn off checking.
Currently it requires that '/proc/loadavg' file exists, otherwise the
load check is bypassed (load is taken to be 0). So platforms that do
not implement '/proc/loadavg' currently cannot use this feature.
Signed-off-by: John 'Warthog9' Hawley <warthog9@kernel.org>
Signed-off-by: Jakub Narebski <redacted>
---
Originally appeared in
http://permalink.gmane.org/gmane.comp.version-control.git/135418
Differences to original version by John 'Warthog9' Hawley (J.H.):
* Slightly improved wording in commit message and in comments
* $maxload is described in "Gitweb config file variables section
in gitweb/README
* You can use '$maxload = undef;' to turn off load checking
* Error page for too high load is generated using die_error, which had
to be extended to handle 503 Service Unavailable HTTP error code
One complaints that didn't get addressed was describing alternate
approaches to just reading '/proc/loadavg', like using BSD::getloadavg
module from CPAN, either in comments in gitweb.perl or in commit
message. But I have changed my mind since then about this issue,
and now I think it is not strictly necessary. I think that
limitations of current approach are described in sufficient detail,
and we have fall back for when used method cannot work.
gitweb/README | 7 ++++++-
gitweb/gitweb.perl | 39 +++++++++++++++++++++++++++++++++++----
2 files changed, 41 insertions(+), 5 deletions(-)
@@ -174,7 +174,7 @@ not include variables usually directly set during build): Base URL for relative URLs in pages generated by gitweb, (e.g. $logo, $favicon, @stylesheets if they are relative URLs), needed and used only for URLs with nonempty PATH_INFO via- <base href="$base_url>. Usually gitweb sets its value correctly,+ <base href="$base_url">. Usually gitweb sets its value correctly, and there is no need to set this variable, e.g. to $my_uri or "/". * $home_link Target of the home link on top of all pages (the first part of view
@@ -228,6 +228,11 @@ not include variables usually directly set during build): repositories from launching cross-site scripting (XSS) attacks. Set this to true if you don't trust the content of your repositories. The default is false.+ * $maxload+ Used to set the maximum load that we will still respond to gitweb queries.+ If server load exceed this value then return "503 Service Unavailable" error.+ Server load is taken to be 0 if gitweb cannot determine its value. Set it to+ undefined value to turn it off. The default is 300. Projects list file format
@@ -221,6 +221,12 @@ our %avatar_size = ('double'=>32);+# Used to set the maximum load that we will still respond to gitweb queries.+# If server load exceed this value then return "503 server busy" error.+# If gitweb cannot determined server load, it is taken to be 0.+# Leave it undefined (or set to 'undef') to turn off load checking.+our$maxload=300;+# You define site-wide feature defaults here; override them with# $GITWEB_CONFIG as necessary.our%feature=(
@@ -551,6 +557,26 @@ if (-e $GITWEB_CONFIG) {do$GITWEB_CONFIG_SYSTEMif-e$GITWEB_CONFIG_SYSTEM;}+# Get loadavg of system, to compare against $maxload.+# Currently it requires '/proc/loadavg' present to get loadavg;+# if it is not present it returns 0, which means no load checking.+subget_loadavg{+openmy$fd,'<','/proc/loadavg'+orreturn0;+my@load=split(/\s+/,scalar<$fd>);+close$fd;++# The first three columns measure CPU and IO utilization of the last one,+# five, and 10 minute periods. The fourth column shows the number of+# currently running processes and the total number of processes in the m/n+# format. The last column displays the last process ID used.+return$load[0]||0;+}++if(defined$maxload&&get_loadavg()>$maxload){+die_error(503,"The load average on the server is too high");+}+# version of the core git binaryour$git_version=qx("$GIT" --version)=~m/git version (.*)$/?$1:"unknown";$number_of_git_cmds++;
@@ -3354,14 +3380,19 @@ sub git_footer_html {# 500: The server isn't configured properly, or# an internal error occurred (e.g. failed assertions caused by bugs), or# an unknown error occurred (e.g. the git binary died unexpectedly).+# 503: The server is currently unavailable (because it is overloaded,+# or down for maintenance). Generally, this is a temporary state.subdie_error{my$status=shift||500;my$error=shift||"Internal server error";-my%http_responses=(400=>'400 Bad Request',-403=>'403 Forbidden',-404=>'404 Not Found',-500=>'500 Internal Server Error');+my%http_responses=(+400=>'400 Bad Request',+403=>'403 Forbidden',+404=>'404 Not Found',+500=>'500 Internal Server Error',+503=>'503 Service Unavailable',+);git_header_html($http_responses{$status});print<<EOF;<divclass="page_body">
Just a heads up I've been on vacation for two weeks and hadn't gotten
around to dealing with these e-mails. I'm going to get them imported
into my tree here and take a look over them.
- John 'Warthog9' Hawley
On 01/03/2010 08:07 AM, Jakub Narebski wrote:
This is resend of early part of "[PATCH 0/6] Gitweb caching changes v2"
thread by John 'Warthog9' Hawley (J.H.),
Message-ID: [off-list ref]
http://thread.gmane.org/gmane.comp.version-control.git/135052
or alternatively
git://git.kernel.org/pub/scm/git/warthog9/gitweb.git gitweb-ml-v2
with a few modifications of my own. Those patches were send originally as
responses in the mentioned thread, for further comments from original
author. As the discussion didn't pick up (because of kernel.org upgrade, and
perhaps due to end-of-year stuff), I am resending those patches in a
separate thread for a better visibility; only comments are changed.
This series of patches is rebased on top of commit 37bae10
(Merge branch 'maint', 2009-12-31) in 'master' branch.
Change that apply to all patches in series:
* moving from "GITWEB - " to "gitweb: " as subsystem prefix
* changing author to John 'Warthog9' Hawley [off-list ref]
(it was John 'Warthog9' Hawley [off-list ref])
* add signoff or change it to John 'Warthog9' Hawley [off-list ref],
and of course add my own signoff.
I have included reply to neither "GITWEB - File based caching layer"
nor "GITWEB - Separate defaults from main file" in this thread/series.
I haven't included the main point of the whole series, namely adding
response caching layer in the form that is used in git.kernel.org, because
I think this patch should be split into smaller parts, and unit-tested.
As it is now it is a bit of mess. I have done patch which makes gitweb
always use explicit filehandle when printing (simplifying a bit it
replaces 'print <something>' by 'print {$out} <something>', with $out set
to \*STDOUT), as a patch that prepares for (optional) gitweb caching, while
not affecting throughput, latency and memory consumption when caching is
disabled, as opposed to original solution by J.H. of always storing whole
response in scalar and writing it at the end.
I haven't included splitting of gitweb_defaults.perl off gitweb.perl, as it
was after large and invasive gitweb caching patch, it would require
substantial changes to gitweb tests upfront (by testing built gitweb.cgi and
not source gitweb.perl), and needs fixing of Makefile to actually work
reliably (we could have to process both gitweb.perl and
gitweb_defaults.perl, while provided Makefile process only the file which
triggered the rule... I think).
I am not sure if 'gitweb: Add option to force version match' is a good
solution to the problem it tires to address, i.e. if it is worth having,
and I am not sure if I did 'gitweb: Makefile improvements' correctly.
John 'Warthog9' Hawley (4):
gitweb: Load checking
gitweb: Add option to force version match
gitweb: Optionally add "git" links in project list page
gitweb: Makefile improvements
Makefile | 65 +++++---------------------
gitweb/Makefile | 129 ++++++++++++++++++++++++++++++++++++++++++++++++++++
gitweb/README | 14 +++++-
gitweb/gitweb.perl | 80 ++++++++++++++++++++++++++++++--
4 files changed, 230 insertions(+), 58 deletions(-)
create mode 100644 gitweb/Makefile
John, any comments?
From: Jakub Narebski <hidden> Date: 2016-06-15 22:47:58
On Wed, 6 Jan 2010, J.H. wrote:
Just a heads up I've been on vacation for two weeks and hadn't gotten
around to dealing with these e-mails. I'm going to get them imported
into my tree here and take a look over them.
They are also available from 'gitweb/cache-kernel' branch of my
git/jnareb-git.git repository at repo.or.cz... and are available from
'pu' branch in main git repository, as fbd43a8^2 (Merge branch
'jh/gitweb-cached' into pu, 2010-01-04).
It might be easier to import (fetch) them from that repository, and just
drop top two commits / merge jnareb-git/gitweb/cache-kernel~2
git://repo.or.cz/git/jnareb-git.git gitweb/cache-kernel
John 'Warthog9' Hawley (4):
gitweb: Load checking
gitweb: Add option to force version match
gitweb: Optionally add "git" links in project list page
gitweb: Makefile improvements
Jakub Narebski (2):
gitweb: Print to explicit filehandle (preparing for caching)
gitweb: href(..., -path_info => 0|1)
The two top commits on that branch are work in progress in preparation
for response caching for gitweb from J.H. (the one used on
git.kernel.org), and are not ready yet, I think; at least there would
be one more commit in "preparing for gitweb caching" (sub)series.
--
Jakub Narebski
Poland