You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -756,7 +756,7 @@ The update command fails if there are changes in your program or library that `m
756
756
757
757
### Updating to an upstream version
758
758
759
-
Before updating a program or a library, it's good to know the names of the stable releases, usually marked with a tag using a common format, e.g. 1.2, v1.0.1, r5.6, mbed-os-5.6, etc.
759
+
Before updating a program or a library, it's good to know the names of the stable releases, usually marked with a tag using a common format, such as `1.2`, `v1.0.1`, `r5.6`, `mbed-os-5.6` and so on.
760
760
761
761
You can find stable release versions of a program or a library using the `mbed releases` command:
You can also recursively list stable releases for your program and libraries using the `-r` switch, e.g. `mbed releases -r`. The output of this command is usually long, thus it's not included in this documentation.
776
+
You can also recursively list stable releases for your program and libraries using the `-r` switch, for example `mbed releases -r`.
777
+
778
+
Lastly, you can list unstable releases, such as release candidates, alphas and betas by using the `-u` switch.
777
779
778
-
Lastly, you can list unstable releases, like release candidates, alphas, betas, using the `-u` switch.
0 commit comments