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, 20 deletions

diff --git a/third_party/git/gitweb/static/js/README b/third_party/git/gitweb/static/js/README
deleted file mode 100644
index f8460ed32fa7..000000000000
--- a/third_party/git/gitweb/static/js/README
+++ /dev/null
@@ -1,20 +0,0 @@
-GIT web interface (gitweb) - JavaScript
-=======================================
-
-This directory holds JavaScript code used by gitweb (GIT web interface).
-Scripts from there would be concatenated together in the order specified
-by gitweb/Makefile into gitweb/static/gitweb.js, during building of
-gitweb/gitweb.cgi (during gitweb building).  The resulting file (or its
-minification) would then be installed / deployed together with gitweb.
-
-Scripts in 'lib/' subdirectory compose generic JavaScript library,
-providing features required by gitweb but in no way limited to gitweb
-only.  In the future those scripts could be replaced by some JavaScript
-library / framework, like e.g. jQuery, YUI, Prototype, MooTools, Dojo,
-ExtJS, Script.aculo.us or SproutCore.
-
-All scripts that manipulate gitweb output should be put outside 'lib/',
-directly in this directory ('gitweb/static/js/').  Those scripts would
-have to be rewritten if gitweb moves to using some JavaScript library.
-
-See also comments in gitweb/Makefile.