An error occurred fetching the project authors.
- 22 Mar, 2018 1 commit
-
-
Ahmad Sherif authored
Closes gitaly#1101
-
- 09 Feb, 2018 1 commit
-
-
Ahmad Sherif authored
Fixes gitlab-development-kit#321
-
- 04 Jan, 2018 1 commit
-
-
Alejandro Rodríguez authored
-
- 28 Dec, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 23 Nov, 2017 1 commit
-
-
Jacob Vosmaer (GitLab) authored
-
- 21 Oct, 2017 1 commit
-
-
Alejandro Rodríguez authored
They're costly. This will also avoid some edge cases where charlock_holmes assigns a weird encoding to a perfectly valid UTF-8 string.
-
- 19 Oct, 2017 1 commit
-
-
Alejandro Rodríguez authored
They're costly. This will also avoid some edge cases where charlock_holmes assigns a weird encoding to a perfectly valid UTF-8 string.
-
- 06 Sep, 2017 5 commits
-
-
micael.bergeron authored
-
micael.bergeron authored
-
micael.bergeron authored
remove some lint
-
micael.bergeron authored
-
micael.bergeron authored
-
- 08 Aug, 2017 1 commit
-
-
Lin Jen-Shin authored
It is recommended that we set this to 50: https://gitlab.com/gitlab-org/gitlab-ce/issues/35098#note_35036746 In this particular issue, the confidence was 42 for Shift JIS, but in fact that's encoded in UTF-8 just with a single bad character. In this case, we shouldn't try to treat it as Shift JIS, but just treat it as UTF-8 and remove invalid bytes. Treating it like Shift JIS would corrupt the whole data. Unfortunately, the diff which would cause this could not be disclosed therefore we can't use it as a test example.
-
- 06 Jun, 2017 1 commit
-
-
James Lopez authored
-
- 01 Jun, 2017 1 commit
-
-
Bob Van Landuyt authored
-