@@ -11,6 +11,11 @@ ephemeral until the repo fixes flow in.
1111
1212This document provides guidance for creating and managing source build patches.
1313
14+ ** NOTE:** Starting with 10.0, the [ Unified Build] ( https://github.com/dotnet/dotnet/blob/main/docs/README.md )
15+ project added support for source edits in the [ VMR] ( https://github.com/dotnet/dotnet ) .
16+ This has eliminated the need for patches as the required changes can be directly made in the VMR.
17+ All changes made to the VMR will automatically flow to the associated repos.
18+
1419## Creating Patches
1520
1621To create a repo patch file, first commit your changes to the source repo (e.g.
@@ -24,10 +29,10 @@ git format-patch --zero-commit --no-signature -1
2429Then, move the patch file into the ` src/SourceBuild/patches/<repo> ` directory of
2530the following repo:
2631
27- * [ .NET 9.0+ ]
28- [ sdk] ( https://github.com/dotnet/sdk/tree/main/src/SourceBuild/patches )
32+ * [ .NET 9.0]
33+ [ sdk] ( https://github.com/dotnet/sdk/tree/release/9.0.1xx )
2934* [ .NET 8.0]
30- [ installer] ( https://github.com/dotnet/installer/tree/main/src/SourceBuild/patches )
35+ [ installer] ( https://github.com/dotnet/installer/tree/release/8.0.1xx )
3136
3237If an existing directory for the repo does not already exist, you will need to
3338create one.
@@ -109,12 +114,3 @@ to be deleted.
1091141. The code being changed or surrounding code was changed - when this happens,
110115the patch will need to be updated. This can be done by manually updating the
111116patch or by re-applying the changes to the repo and recreating the patch.
112-
113- ## Unified Build Plans
114-
115- The [Unified
116- Build](https://github.com/dotnet/dotnet/blob/main/docs/README.md)
117- project will add support for source edits in the
118- [VMR](https://github.com/dotnet/dotnet). This will eliminate the need for
119- patches as the required changes can be directly made in the VMR. All changes
120- made to the VMR will automatically flow to the associated repos.
0 commit comments