aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorGabor Pali <pgj@FreeBSD.org>2013-05-12 19:57:08 +0000
committerGabor Pali <pgj@FreeBSD.org>2013-05-12 19:57:08 +0000
commitc8adcb590ae7125c8651be15f4889310dfaaf059 (patch)
tree4bb5c1c2b995a2b50fc30c416667427bddc2ec85 /UPDATING
parentb4c6a782d90e4f2222ceacb4a0a6541662922ee2 (diff)
downloadports-c8adcb590ae7125c8651be15f4889310dfaaf059.tar.gz
ports-c8adcb590ae7125c8651be15f4889310dfaaf059.zip
Notes
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING4
1 files changed, 2 insertions, 2 deletions
diff --git a/UPDATING b/UPDATING
index d849fe06cf29..7e1fbb2264d9 100644
--- a/UPDATING
+++ b/UPDATING
@@ -14,11 +14,11 @@ you update your ports collection, before attempting any port upgrades.
/sbin/sha256. The result of this is silent data corruption.
This problem has been fixed, but every file stored in an annex
- repository will fail a `git annex fsck` after the upgrade. Thus,
+ repository will fail a `git-annex fsck` after the upgrade. Thus,
before updating, it is wise to issue the command below and restore the
files.
- $ git annex uninit
+ $ git-annex uninit
Corruptions can then be found by finding all files with the same hash.
Note that only files that were mishashed to the same location are a