Blame SOURCES/vstest-use-work-tree-with-git-apply.patch

9939d1
From b2c4b2427d8c1a2410c4210789caccf1ec87e64a Mon Sep 17 00:00:00 2001
9939d1
From: Omair Majid <omajid@redhat.com>
9939d1
Date: Thu, 9 Sep 2021 13:21:51 -0400
9939d1
Subject: [PATCH] [ArPow] Use --work-tree with git apply
9939d1
9939d1
This makes things work better in a source-tarball build, where there may
9939d1
be a .git directory somewhere in our parent directories but it's for a
9939d1
different repo than vstest. In a situation like that a plain `git apply`
9939d1
will (silently!) ignore patches because they wont apply to the unrelated
9939d1
repository. That will (eventually) make the source-build fail.
9939d1
`--work-tree` makes git directly use the directory that we care about.
9939d1
9939d1
See https://github.com/dotnet/source-build/issues/2445 for more details.
9939d1
---
9939d1
 eng/SourceBuild.props | 2 +-
9939d1
 1 file changed, 1 insertion(+), 1 deletion(-)
9939d1
9939d1
diff --git a/eng/SourceBuild.props b/eng/SourceBuild.props
9939d1
index b365645c..68f82592 100644
9939d1
--- a/eng/SourceBuild.props
9939d1
+++ b/eng/SourceBuild.props
9939d1
@@ -24,7 +24,7 @@
9939d1
     </ItemGroup>
9939d1
 
9939d1
     
9939d1
-      Command="git apply --ignore-whitespace --whitespace=nowarn "%(SourceBuildPatchFile.FullPath)""
9939d1
+      Command="git --work-tree="$(InnerSourceBuildRepoRoot)" apply --ignore-whitespace --whitespace=nowarn "%(SourceBuildPatchFile.FullPath)""
9939d1
       WorkingDirectory="$(InnerSourceBuildRepoRoot)"
9939d1
       Condition="'@(SourceBuildPatchFile)' != ''" />
9939d1
   </Target>
9939d1
-- 
9939d1
2.31.1
9939d1