An error occurred fetching the project authors.
- 22 Jan, 2014 10 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Remove Old Twitter
-
dosire authored
-
Dmitriy Zaporozhets authored
Updated gitlab.yaml.example's issue_closing_pattern to single quotes
-
- 21 Jan, 2014 11 commits
-
-
Sytse Sijbrandij authored
Explain how to use userPrincipalName as the username with AD
-
Jacob Vosmaer authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Jacob Vosmaer authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Added support for Go's repository retrieval.
-
Sytse Sijbrandij authored
Rephrase LDAP check script output
-
Jacob Vosmaer authored
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.
-
Dmitriy Zaporozhets authored
Changelog Base64 Add O'Reilly sponsorship in CHANGELOG
-
Marc Radulescu authored
-
- 20 Jan, 2014 19 commits
-
-
Jacob Vosmaer authored
Explain where the memory recommendation comes from The 250MB repo limit is caused by the git command line. Also see MR !422
-
Dmitriy Zaporozhets authored
Rename "Website url" labels to "Website"
-
Dmitriy Zaporozhets authored
Encouragement during install
-
Dmitriy Zaporozhets authored
Fix select2 css for drop above style less than a minute ago
-
Dmitriy Zaporozhets authored
Fix 500 error on project issues and merge requests pages
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Jerome Dalbert authored
-
Bruno Albuquerque authored
-
Dmitriy Zaporozhets authored
Fix assign-to-me link for MergeRequest form
-
Dmitriy Zaporozhets authored
Import Doc
-
dosire authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Sytse Sijbrandij authored
Git clone performance is still the same
-
Jacob Vosmaer authored
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.
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Bruno Albuquerque authored
-
Dmitriy Zaporozhets authored
-
Bruno Albuquerque authored
-