summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-10-14 13:44:20 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-10-14 13:44:20 -0400
commit592b273629f84c24ccd4eb1d50c5c00272bfcd7b (patch)
treec16eb4b61d688a902af9e7dbafc2a3c65bf33fbc
parenteb4b68a8f4309817939491fb7545432e87817529 (diff)
word wrap
-rw-r--r--doc/upgrades.mdwn23
1 files changed, 18 insertions, 5 deletions
diff --git a/doc/upgrades.mdwn b/doc/upgrades.mdwn
index 9fb56f62b..f5e9cbc3a 100644
--- a/doc/upgrades.mdwn
+++ b/doc/upgrades.mdwn
@@ -2,11 +2,24 @@
# Software upgrades
-Upgrading the code base of git-annex will be done differently depending on your [[install]] method. For most distribution-based packages, it is handled by the package management software.
-
-For the standalone distribution, the [[git-annex-webapp]](1) will ask the user for confirmation when it detects a new version. Once that is confirmed, or if `annex.autoupgrade` is enabled (see the [[git-annex]](1) manpage) the assistant will start the upgrade. The upgrade process is fairly simple: the assistant will move the `git-annex.linux` directory out of the way and replace it with the new version, then re-execute itself. It therefore needs write access to the parent directory of the `git-annex.linux` directory.
-
-Note that "upgrading" from a distribution-based package to the [[install/Linux_standalone/]] version may cause weird problems, as an unexpected version of git-annex (e.g. the old one from packages) may be ran, see [[bugs/git-annex-shell_doesn__39__t_work_as_expected/]] for a full discussion.
+Upgrading the code base of git-annex will be done differently depending on
+your [[install]] method. For most distribution-based packages, it is
+handled by the package management software.
+
+For the standalone distribution, the [[git-annex-webapp]](1) will ask the
+user for confirmation when it detects a new version. Once that is
+confirmed, or if `annex.autoupgrade` is enabled (see the [[git-annex]](1)
+manpage) the assistant will start the upgrade. The upgrade process is
+fairly simple: the assistant will move the `git-annex.linux` directory out
+of the way and replace it with the new version, then re-execute itself. It
+therefore needs write access to the parent directory of the
+`git-annex.linux` directory.
+
+Note that "upgrading" from a distribution-based package to the
+[[install/Linux_standalone/]] version may cause weird problems, as an
+unexpected version of git-annex (e.g. the old one from packages) may be
+ran, see [[bugs/git-annex-shell_doesn__39__t_work_as_expected/]] for a full
+discussion.
# Repository upgrades