summaryrefslogtreecommitdiff
path: root/doc/development/git_object_deduplication.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/development/git_object_deduplication.md')
-rw-r--r--doc/development/git_object_deduplication.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/development/git_object_deduplication.md b/doc/development/git_object_deduplication.md
index d9ff88aef60..1607f3e7a12 100644
--- a/doc/development/git_object_deduplication.md
+++ b/doc/development/git_object_deduplication.md
@@ -35,9 +35,9 @@ to work, it is of course critical that **no objects ever get deleted from
B** because A might need them.
WARNING:
-Do not run `git prune` or `git gc` in pool repositories! This can
-cause data loss in "real" repositories that depend on the pool in
-question.
+Do not run `git prune` or `git gc` in object pool repositories, which are
+stored in the `@pools` directory. This can cause data loss in the regular
+repositories that depend on the object pool.
The danger lies in `git prune`, and `git gc` calls `git prune`. The
problem is that `git prune`, when running in a pool repository, cannot
@@ -45,8 +45,8 @@ reliable decide if an object is no longer needed.
### Git alternates in GitLab: pool repositories
-GitLab organizes this object borrowing by creating special **pool
-repositories** which are hidden from the user. We then use Git
+GitLab organizes this object borrowing by [creating special **pool
+repositories**](../administration/repository_storage_types.md) which are hidden from the user. We then use Git
alternates to let a collection of project repositories borrow from a
single pool repository. We call such a collection of project
repositories a pool. Pools form star-shaped networks of repositories