chore(3p/git): Unvendor git and track patches instead r/2903

This was vendored a long time ago under the expectation that keeping
it in sync with cgit would be easier this way, but it has proven not
to be a big issue.

On the other hand, a vendored copy of git is an annoying maintenance
burden. It is much easier to rebase the single (dottime) patch that we
have.

This removes the vendored copy of git and instead passes the git
source code to cgit via `pkgs.srcOnly`, which includes the applied
patch so that cgit can continue rendering dottime.

Change-Id: If31f62dea7ce688fd1b9050204e9378019775f2b

1 files changed, 0 insertions, 70 deletions

diff --git a/third_party/git/gitweb/README b/third_party/git/gitweb/README
deleted file mode 100644
index 471dcfb691bb..000000000000
--- a/third_party/git/gitweb/README
+++ /dev/null
@@ -1,70 +0,0 @@
-GIT web Interface
-=================
-
-From the git version 1.4.0 gitweb is bundled with git.
-
-
-Build time gitweb configuration
--------------------------------
-There are many configuration variables which affect building gitweb (among
-others creating gitweb.cgi out of gitweb.perl by replacing placeholders such
-as `++GIT_BINDIR++` by their build-time values).
-
-Building and installing gitweb is described in gitweb's INSTALL file
-(in 'gitweb/INSTALL').
-
-
-Runtime gitweb configuration
-----------------------------
-Gitweb obtains configuration data from the following sources in the
-following order:
-
-1. built-in values (some set during build stage),
-2. common system-wide configuration file (`GITWEB_CONFIG_COMMON`,
-   defaults to '/etc/gitweb-common.conf'),
-3. either per-instance configuration file (`GITWEB_CONFIG`, defaults to
-   'gitweb_config.perl' in the same directory as the installed gitweb),
-   or if it does not exists then system-wide configuration file
-   (`GITWEB_CONFIG_SYSTEM`, defaults to '/etc/gitweb.conf').
-
-Values obtained in later configuration files override values obtained earlier
-in above sequence.
-
-You can read defaults in system-wide GITWEB_CONFIG_SYSTEM from GITWEB_CONFIG
-by adding
-
-  read_config_file($GITWEB_CONFIG_SYSTEM);
-
-at very beginning of per-instance GITWEB_CONFIG file.  In this case
-settings in said per-instance file will override settings from
-system-wide configuration file.  Note that read_config_file checks
-itself that the $GITWEB_CONFIG_SYSTEM file exists.
-
-The most notable thing that is not configurable at compile time are the
-optional features, stored in the '%features' variable.
-
-Ultimate description on how to reconfigure the default features setting
-in your `GITWEB_CONFIG` or per-project in `project.git/config` can be found
-as comments inside 'gitweb.cgi'.
-
-See also gitweb.conf(5) manpage.
-
-
-Web server configuration
-------------------------
-Gitweb can be run as CGI script, as legacy mod_perl application (using
-ModPerl::Registry), and as FastCGI script.  You can find some simple examples
-in "Example web server configuration" section in INSTALL file for gitweb (in
-gitweb/INSTALL).
-
-See "Webserver configuration" and "Advanced web server setup" sections in
-gitweb(1) manpage.
-
-
-AUTHORS
--------
-Originally written by:
-  Kay Sievers <kay.sievers@vrfy.org>
-
-Any comment/question/concern to:
-  Git mailing list <git@vger.kernel.org>