summaryrefslogtreecommitdiff
path: root/doc/tips/antipatterns.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/tips/antipatterns.mdwn')
-rw-r--r--doc/tips/antipatterns.mdwn18
1 files changed, 8 insertions, 10 deletions
diff --git a/doc/tips/antipatterns.mdwn b/doc/tips/antipatterns.mdwn
index 04504ac9c..8e8a98acb 100644
--- a/doc/tips/antipatterns.mdwn
+++ b/doc/tips/antipatterns.mdwn
@@ -11,13 +11,11 @@ possible ways of doing things.
[[!toc]]
-.git/annex symlink
-==================
+---
-Antipattern
------------
+# **Antipattern**
-Symlinking the `.git/annex` symlink directory, in the hope of saving
+Symlinking the `.git/annex` directory, in the hope of saving
disk space, is a horrible idea. The general antipattern is:
git clone repoA repoB
@@ -54,8 +52,11 @@ Probably no way to fix this in git-annex - if users want to shoot
themselves in the foot by messing with the backend, there's not much
we can do to change that in this case.
-using reinit with an existing uuid without fsck
-===============================================
+---
+
+# **Antipattern**
+
+Reinit repo with an existing uuid without fsck
To quote the [[git-annex-reinit]] manpage:
@@ -64,9 +65,6 @@ To quote the [[git-annex-reinit]] manpage:
> to reuse a UUID -- for example, if a repository got deleted, and
> you're setting it back up.
-Anti-pattern
-------------
-
[[git-annex-reinit]] can be used to reuse UUIDs for deleted
repositories. But what happens if you reuse the UUID of an *existing*
repository, or a repository that hasn't been properly emptied before