Replace 6.0-to-6.4.md with 6.0-to-6.5.md

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Remove Old Twitter

Updated gitlab.yaml.example's issue_closing_pattern to single quotes

Explain how to use userPrincipalName as the username with AD

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

 Added support for Go's repository retrieval.

Rephrase LDAP check script output

The previous phrasing lead some people to believe that there is a limit
on the number of LDAP users that can sign in to a GitLab instance. That
is not the case; the limit in the check script only applies to the
diagnostic information result set, so that running `rake gitlab:check`
does not output thousands of LDAP users.

Changelog Base64

Add O'Reilly sponsorship in CHANGELOG

Explain where the memory recommendation comes from

The 250MB repo limit is caused by the git command line.

Also see MR !422

Rename "Website url" labels to "Website"

Encouragement during install

Fix select2 css for drop above style less than a minute ago

Fix 500 error on project issues and merge requests pages

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Fix assign-to-me link for MergeRequest form

Import Doc

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Git clone performance is still the same

This reverts commit a757c4a2.

While it is true that Grack memory use while sending data to a client
was improved, this does not change the fact that the Git processes
running on a GitLab server will use more memory for large repositories.

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>