diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2018-04-16 14:05:39 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2018-04-16 14:05:39 +0200 |
| commit | d20fe9380f74f83269d3c8cceffc94406c6216f9 (patch) | |
| tree | 51ea41d8467e766da018dd468cc3c6ddaf0b472f /UPGRADE.cli | |
| parent | 18bd6cbdec7ac41a6506d803d921abac1eb718a1 (diff) | |
Use note formatting in installation and upgrade guide
Diffstat (limited to 'UPGRADE.cli')
| -rw-r--r-- | UPGRADE.cli | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/UPGRADE.cli b/UPGRADE.cli index 01444d5..da078b2 100644 --- a/UPGRADE.cli +++ b/UPGRADE.cli @@ -26,10 +26,11 @@ old toolchain, install the new toolchain as \"final\", and finally uninstall We recommend that you use a dirty upgrade for patch releases with the same \c{X.Y} (\c{MAJOR.MINOR}) version and a staged upgrade otherwise. With patch -releases we guarantee not to alter the installation file set. Note also that -without periodic upgrades your version of the toolchain may become too old to -be able to upgrade itself. In this case you will have to fall back onto the -bootstrap process. +releases we guarantee not to alter the installation file set. + +\N|Note that without periodic upgrades your version of the toolchain may +become too old to be able to upgrade itself. In this case you will have to +fall back onto the bootstrap process.| The dirty upgrade is straightforward: |