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

diff --git a/third_party/git/Documentation/RelNotes/1.7.9.3.txt b/third_party/git/Documentation/RelNotes/1.7.9.3.txt
deleted file mode 100644
index 91c65012f981..000000000000
--- a/third_party/git/Documentation/RelNotes/1.7.9.3.txt
+++ /dev/null
@@ -1,51 +0,0 @@
-Git v1.7.9.3 Release Notes
-==========================
-
-Fixes since v1.7.9.2
---------------------
-
- * "git p4" (in contrib/) submit the changes to a wrong place when the
-   "--use-client-spec" option is set.
-
- * The config.mak.autogen generated by optional autoconf support tried
-   to link the binary with -lintl even when libintl.h is missing from
-   the system.
-
- * When the filter driver exits before reading the content before the
-   main git process writes the contents to be filtered to the pipe to
-   it, the latter could be killed with SIGPIPE instead of ignoring
-   such an event as an error.
-
- * "git add --refresh <pathspec>" used to warn about unmerged paths
-   outside the given pathspec.
-
- * The bulk check-in codepath in "git add" streamed contents that
-   needs smudge/clean filters without running them, instead of punting
-   and delegating to the codepath to run filters after slurping
-   everything to core.
-
- * "git branch --with $that" assumed incorrectly that the user will never
-   ask the question with nonsense value in $that.
-
- * "git bundle create" produced a corrupt bundle file upon seeing
-   commits with excessively long subject line.
-
- * When a remote helper exits before reading the blank line from the
-   main git process to signal the end of commands, the latter could be
-   killed with SIGPIPE. Instead we should ignore such event as a
-   non-error.
-
- * The commit log template given with "git merge --edit" did not have
-   a short instructive text like what "git commit" gives.
-
- * "git rev-list --verify-objects -q" omitted the extra verification
-   it needs to do over "git rev-list --objects -q" by mistake.
-
- * "gitweb" used to drop warnings in the log file when "heads" view is
-   accessed in a repository whose HEAD does not point at a valid
-   branch.
-
- * An invalid regular expression pattern given by an end user made
-   "gitweb" to return garbled response.
-
-Also contains minor fixes and documentation updates.