diff options
| author | Douwe Maan <douwe@gitlab.com> | 2017-11-01 17:51:50 +0000 |
|---|---|---|
| committer | Douwe Maan <douwe@gitlab.com> | 2017-11-01 17:51:50 +0000 |
| commit | 1401ec2186bb7038669903814e4bf44a1472fe5c (patch) | |
| tree | eb012865005d254da68dd7fdfb1e507cb02cf563 | |
| parent | e65bbc0ca48aebcf06b83ffd2cb2cfaa6f5ed102 (diff) | |
| parent | c57a7cafc172e399d1122883f9c61a46ba376abe (diff) | |
| download | gitlab-ce-1401ec2186bb7038669903814e4bf44a1472fe5c.tar.gz | |
Merge branch 'patch-29' into 'master'
Fix typo
See merge request gitlab-org/gitlab-ce!15136
| -rw-r--r-- | doc/administration/repository_storage_types.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/administration/repository_storage_types.md b/doc/administration/repository_storage_types.md index 0cb2648cc1e..bc9b6253f1a 100644 --- a/doc/administration/repository_storage_types.md +++ b/doc/administration/repository_storage_types.md @@ -76,7 +76,7 @@ To migrate your existing projects to the new storage type, check the specific [r We are incrementally moving every storable object in GitLab to the Hashed Storage pattern. You can check the current coverage status below. -Not that things stored in S3 compatible endpoint, will not have the downsides mentioned earlier, if they are not +Note that things stored in an S3 compatible endpoint will not have the downsides mentioned earlier, if they are not prefixed with `#{namespace}/#{project_name}`, which is true for CI Cache and LFS Objects. | Storable Object | Legacy Storage | Hashed Storage | S3 Compatible | GitLab Version | |