- 13 10月, 2017 2 次提交
-
-
由 Alejandro Rodríguez 提交于
Rename classes to (hopefully) clearer names while we're doing that.
-
由 Alejandro Rodríguez 提交于
This prepares the codebase for a Gitaly migration. See https://gitlab.com/gitlab-org/gitaly/issues/553
-
- 27 7月, 2017 2 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Rémy Coutable 提交于
Remove superfluous lib: true, type: redis, service: true, models: true, services: true, no_db: true, api: true Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 18 7月, 2017 1 次提交
-
-
由 Luke "Jared" Bennett 提交于
-
- 17 7月, 2017 1 次提交
-
-
由 Luke "Jared" Bennett 提交于
-
- 21 6月, 2017 1 次提交
-
-
由 Grzegorz Bizon 提交于
-
- 15 3月, 2017 1 次提交
-
-
由 Sean McGivern 提交于
We wanted to check that the text could be encoded as JSON, because conflict resolutions are passed back and forth in that format, so the file itself must be UTF-8. However, all strings from the repository come back without an encoding from Rugged, making them ASCII_8BIT. We force to UTF-8, and reject if it's invalid. This still leaves the problem of a file that 'looks like' UTF-8 (contains valid UTF-8 byte sequences), but isn't. However: 1. If the conflicts contain the problem bytes, the user will see that the file isn't displayed correctly. 2. If the problem bytes are outside of the conflict area, then we will write back the same bytes when we resolve the conflicts, even though we though the encoding was UTF-8.
-
- 23 2月, 2017 2 次提交
-
-
由 Douwe Maan 提交于
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
由 Douwe Maan 提交于
-
- 07 9月, 2016 1 次提交
-
-
由 Sean McGivern 提交于
-
- 25 8月, 2016 1 次提交
-
-
由 Sean McGivern 提交于
These can't be resolved in the UI because if they aren't in a UTF-8 compatible encoding, they can't be rendered as JSON. Even if they could, we would be implicitly changing the file encoding anyway, which seems like a bad idea.
-
- 13 8月, 2016 3 次提交
-
-
由 Sean McGivern 提交于
-
由 Sean McGivern 提交于
-
由 Sean McGivern 提交于
-