aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/tips/deleting_unwanted_files.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/tips/deleting_unwanted_files.mdwn b/doc/tips/deleting_unwanted_files.mdwn
index 5fa197c54..c83b960da 100644
--- a/doc/tips/deleting_unwanted_files.mdwn
+++ b/doc/tips/deleting_unwanted_files.mdwn
@@ -6,7 +6,7 @@ With git-annex this changes some: Very large files can be managed with git-annex
In this method, you just remove annexed files whenever you want, and commit the changes. This is probably the most natural way to go.
-In an indirect mode repo, you can do this the same way you would in a regular git repository. For example, `git rm foo; git commit -m "removed foo". This leaves the contents of the files still in the annex, not really deleted yet.
+In an indirect mode repo, you can do this the same way you would in a regular git repository. For example, `git rm foo; git commit -m "removed foo"`. This leaves the contents of the files still in the annex, not really deleted yet.
If you have a direct mode repo, you can't run `git rm` in it. Instead, you can just delete files using `rm` or your file manager, and then run `git annex sync` to commit the deletion. That will delete the file's content from your disk. Even if it's the only copy of the file!