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

diff --git a/third_party/git/perl/Git/SVN/Memoize/YAML.pm b/third_party/git/perl/Git/SVN/Memoize/YAML.pm
deleted file mode 100644
index 9676b8f2f735..000000000000
--- a/third_party/git/perl/Git/SVN/Memoize/YAML.pm
+++ /dev/null
@@ -1,93 +0,0 @@
-package Git::SVN::Memoize::YAML;
-use warnings;
-use strict;
-use YAML::Any ();
-
-# based on Memoize::Storable.
-
-sub TIEHASH {
-	my $package = shift;
-	my $filename = shift;
-	my $truehash = (-e $filename) ? YAML::Any::LoadFile($filename) : {};
-	my $self = {FILENAME => $filename, H => $truehash};
-	bless $self => $package;
-}
-
-sub STORE {
-	my $self = shift;
-	$self->{H}{$_[0]} = $_[1];
-}
-
-sub FETCH {
-	my $self = shift;
-	$self->{H}{$_[0]};
-}
-
-sub EXISTS {
-	my $self = shift;
-	exists $self->{H}{$_[0]};
-}
-
-sub DESTROY {
-	my $self = shift;
-	YAML::Any::DumpFile($self->{FILENAME}, $self->{H});
-}
-
-sub SCALAR {
-	my $self = shift;
-	scalar(%{$self->{H}});
-}
-
-sub FIRSTKEY {
-	'Fake hash from Git::SVN::Memoize::YAML';
-}
-
-sub NEXTKEY {
-	undef;
-}
-
-1;
-__END__
-
-=head1 NAME
-
-Git::SVN::Memoize::YAML - store Memoized data in YAML format
-
-=head1 SYNOPSIS
-
-    use Memoize;
-    use Git::SVN::Memoize::YAML;
-
-    tie my %cache => 'Git::SVN::Memoize::YAML', $filename;
-    memoize('slow_function', SCALAR_CACHE => [HASH => \%cache]);
-    slow_function(arguments);
-
-=head1 DESCRIPTION
-
-This module provides a class that can be used to tie a hash to a
-YAML file.  The file is read when the hash is initialized and
-rewritten when the hash is destroyed.
-
-The intent is to allow L<Memoize> to back its cache with a file in
-YAML format, just like L<Memoize::Storable> allows L<Memoize> to
-back its cache with a file in Storable format.  Unlike the Storable
-format, the YAML format is platform-independent and fairly stable.
-
-Carps on error.
-
-=head1 DIAGNOSTICS
-
-See L<YAML::Any>.
-
-=head1 DEPENDENCIES
-
-L<YAML::Any> from CPAN.
-
-=head1 INCOMPATIBILITIES
-
-None reported.
-
-=head1 BUGS
-
-The entire cache is read into a Perl hash when loading the file,
-so this is not very scalable.