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

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