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

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