From: Fadi Hanna <fadim@microsoft.com>
Date: Thu, 5 Dec 2019 20:06:21 +0000 (-0800)
Subject: Fix inaccurate comment. (#585)
X-Git-Tag: submit/tizen/20210909.063632~10792
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=b4e7657f5d21c4ff2bd3860a4b4cc5d494aa6d8f;p=platform%2Fupstream%2Fdotnet%2Fruntime.git

Fix inaccurate comment. (#585)

Crossgen2 is in its own package, not included with the runtime package
---

diff --git a/src/coreclr/src/.nuget/Microsoft.NETCore.Crossgen2/Microsoft.NETCore.Crossgen2.pkgproj b/src/coreclr/src/.nuget/Microsoft.NETCore.Crossgen2/Microsoft.NETCore.Crossgen2.pkgproj
index ad0230f..f10cd21 100644
--- a/src/coreclr/src/.nuget/Microsoft.NETCore.Crossgen2/Microsoft.NETCore.Crossgen2.pkgproj
+++ b/src/coreclr/src/.nuget/Microsoft.NETCore.Crossgen2/Microsoft.NETCore.Crossgen2.pkgproj
@@ -11,10 +11,9 @@
   <Import Project="$([MSBuild]::GetPathOfFileAbove(Directory.Build.targets))" />
 
   <PropertyGroup>
-    <!-- We're publishing crossgen2 as framework dependent application in the runtime package for now since we only have
+    <!-- We're publishing crossgen2 in its own package as framework dependent application for now since we only have
         two simple scenarios we want to support in the short term: win_x64 to win_x64 and linux_x64 to linux_x64 compilations.
-        Once we have more complex targets, especially cross-platform and cross-architecture, crossgen2 should move to its own
-        package, and become a self-contained package.
+        Once we have more complex targets, especially cross-platform and cross-architecture, crossgen2 will become a self-contained package.
     -->
     <Crossgen2RuntimeConfigContents>
 {