summaryrefslogtreecommitdiff
path: root/doc/user
diff options
context:
space:
mode:
authorChristian Couder <chriscool@tuxfamily.org>2018-02-26 17:58:57 +0000
committerChristian Couder <chriscool@tuxfamily.org>2018-03-01 16:38:43 +0100
commitcc7b50265a1b5286b18c7627cefd28807d834ea7 (patch)
treebd205c95aa5e246e37b639f3ab48eadb86d16470 /doc/user
parentd412b90af0ff59c6c379fb83727cc23043c42cdc (diff)
downloadgitlab-ce-cc7b50265a1b5286b18c7627cefd28807d834ea7.tar.gz
perforce.md: add note about repackingpatch-28
Diffstat (limited to 'doc/user')
-rw-r--r--doc/user/project/import/perforce.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/user/project/import/perforce.md b/doc/user/project/import/perforce.md
index aa7508e1e8e..a1ea716b606 100644
--- a/doc/user/project/import/perforce.md
+++ b/doc/user/project/import/perforce.md
@@ -48,3 +48,9 @@ Here's a few links to get you started:
- [git-p4 manual page](https://www.kernel.org/pub/software/scm/git/docs/git-p4.html)
- [git-p4 example usage](https://git.wiki.kernel.org/index.php/Git-p4_Usage)
- [Git book migration guide](https://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git#_perforce_import)
+
+Note that `git p4` and `git filter-branch` are not very good at
+creating small and efficient Git pack files. So it might be a good
+idea to spend time and CPU to properly repack your repository before
+sending it for the first time to your GitLab server. See
+[this StackOverflow question](https://stackoverflow.com/questions/28720151/git-gc-aggressive-vs-git-repack/).