Skip to content

Commit a386ae2

Browse files
atsushikansafern
authored andcommitted
Fix git command in README (#638)
1 parent 02a52f2 commit a386ae2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Documentation/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ The .NET Core Runtime consists of 4 repos, core-setup at the top of the stack (w
6666
This means that in order to get a runtime you'll need to build the source-build repo with the `/p:RootRepo=core-setup` parameter, this will automatically build coreclr, standard and corefx. Source-Build is composed by git submodules, so the first thing you need to run before doing anything is:
6767

6868
```console
69-
git submodule --init --recursive
69+
git submodule update --init --recursive
7070
```
7171

7272
This will initialize the submodules and clone the repos under the src folder if they haven't been initialized. Note that this will update every submodule to their tracking commit checked in to the `source-build` repo . However you can go to each repo indivually, add custom remotes and checkout certain branches containing your changes.
@@ -200,4 +200,4 @@ In order to run the app you have two options:
200200
- Run `dotnet publish -r RID`. You more information about publish and RID in [this guide](https://docs.microsoft.com/en-us/dotnet/core/rid-catalog).
201201
- Run produced executable in publish directory.
202202
2. Use `dotnet run`:
203-
- In order to use `dotnet run` you will have to install the produced runtime before running the app. Note that installing the runtime, whenever a real runtime for the current produced version is released, if you forget to delete/uninstall the custom runtime, it could cause issues.
203+
- In order to use `dotnet run` you will have to install the produced runtime before running the app. Note that installing the runtime, whenever a real runtime for the current produced version is released, if you forget to delete/uninstall the custom runtime, it could cause issues.

0 commit comments

Comments
 (0)