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

diff --git a/third_party/git/Documentation/RelNotes/1.7.12.2.txt b/third_party/git/Documentation/RelNotes/1.7.12.2.txt
deleted file mode 100644
index 69255745e6ea..000000000000
--- a/third_party/git/Documentation/RelNotes/1.7.12.2.txt
+++ /dev/null
@@ -1,40 +0,0 @@
-Git 1.7.12.2 Release Notes
-==========================
-
-Fixes since v1.7.12.1
----------------------
-
- * When "git am" is fed an input that has multiple "Content-type: ..."
-   header, it did not grok charset= attribute correctly.
-
- * Even during a conflicted merge, "git blame $path" always meant to
-   blame uncommitted changes to the "working tree" version; make it
-   more useful by showing cleanly merged parts as coming from the other
-   branch that is being merged.
-
- * "git blame MAKEFILE" run in a history that has "Makefile" but not
-   "MAKEFILE" should say "No such file MAKEFILE in HEAD", but got
-   confused on a case insensitive filesystem and failed to do so.
-
- * "git fetch --all", when passed "--no-tags", did not honor the
-   "--no-tags" option while fetching from individual remotes (the same
-   issue existed with "--tags", but combination "--all --tags" makes
-   much less sense than "--all --no-tags").
-
- * "git log/diff/format-patch --stat" showed the "N line(s) added"
-   comment in user's locale and caused careless submitters to send
-   patches with such a line in them to projects whose project language
-   is not their language, mildly irritating others. Localization to
-   the line has been disabled for now.
-
- * "git log --all-match --grep=A --grep=B" ought to show commits that
-   mention both A and B, but when these three options are used with
-   --author or --committer, it showed commits that mention either A or
-   B (or both) instead.
-
- * The subcommand to remove the definition of a remote in "git remote"
-   was named "rm" even though all other subcommands were spelled out.
-   Introduce "git remote remove" to remove confusion, and keep "rm" as
-   a backward compatible synonym.
-
-Also contains a handful of documentation updates.