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

diff --git a/third_party/git/Documentation/RelNotes/1.9.5.txt b/third_party/git/Documentation/RelNotes/1.9.5.txt
deleted file mode 100644
index 8d6ac0cf5357..000000000000
--- a/third_party/git/Documentation/RelNotes/1.9.5.txt
+++ /dev/null
@@ -1,34 +0,0 @@
-Git v1.9.5 Release Notes
-========================
-
-Fixes since v1.9.4
-------------------
-
- * We used to allow committing a path ".Git/config" with Git that is
-   running on a case sensitive filesystem, but an attempt to check out
-   such a path with Git that runs on a case insensitive filesystem
-   would have clobbered ".git/config", which is definitely not what
-   the user would have expected.  Git now prevents you from tracking
-   a path with ".Git" (in any case combination) as a path component.
-
- * On Windows, certain path components that are different from ".git"
-   are mapped to ".git", e.g. "git~1/config" is treated as if it were
-   ".git/config".  HFS+ has a similar issue, where certain unicode
-   codepoints are ignored, e.g. ".g\u200cit/config" is treated as if
-   it were ".git/config".  Pathnames with these potential issues are
-   rejected on the affected systems.  Git on systems that are not
-   affected by this issue (e.g. Linux) can also be configured to
-   reject them to ensure cross platform interoperability of the hosted
-   projects.
-
- * "git fsck" notices a tree object that records such a path that can
-   be confused with ".git", and with receive.fsckObjects configuration
-   set to true, an attempt to "git push" such a tree object will be
-   rejected.  Such a path may not be a problem on a well behaving
-   filesystem but in order to protect those on HFS+ and on case
-   insensitive filesystems, this check is enabled on all platforms.
-
-A big "thanks!" for bringing this issue to us goes to our friends in
-the Mercurial land, namely, Matt Mackall and Augie Fackler.
-
-Also contains typofixes, documentation updates and trivial code clean-ups.