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

diff --git a/third_party/git/t/t5311-pack-bitmaps-shallow.sh b/third_party/git/t/t5311-pack-bitmaps-shallow.sh
deleted file mode 100755
index 872a95df3383..000000000000
--- a/third_party/git/t/t5311-pack-bitmaps-shallow.sh
+++ /dev/null
@@ -1,39 +0,0 @@
-#!/bin/sh
-
-test_description='check bitmap operation with shallow repositories'
-. ./test-lib.sh
-
-# We want to create a situation where the shallow, grafted
-# view of reachability does not match reality in a way that
-# might cause us to send insufficient objects.
-#
-# We do this with a history that repeats a state, like:
-#
-#      A    --   B    --   C
-#    file=1    file=2    file=1
-#
-# and then create a shallow clone to the second commit, B.
-# In a non-shallow clone, that would mean we already have
-# the tree for A. But in a shallow one, we've grafted away
-# A, and fetching A to B requires that the other side send
-# us the tree for file=1.
-test_expect_success 'setup shallow repo' '
-	echo 1 >file &&
-	git add file &&
-	git commit -m orig &&
-	echo 2 >file &&
-	git commit -a -m update &&
-	git clone --no-local --bare --depth=1 . shallow.git &&
-	echo 1 >file &&
-	git commit -a -m repeat
-'
-
-test_expect_success 'turn on bitmaps in the parent' '
-	git repack -adb
-'
-
-test_expect_success 'shallow fetch from bitmapped repo' '
-	(cd shallow.git && git fetch)
-'
-
-test_done