GitLab

Created by: SaitoWu

Relate to:

https://github.com/gitlabhq/gitlabhq/commit/cda5e66d7c190e852b23caca17d90df43d91d75e#commitcomment-2107925

update

We have two problems:

backend => ruby and frontend => coffee

This PR will fix backend problem

need to fix jquery.history plugin to solve the frontend problem

cc/ @tsigo

Created by: SaitoWu

close this one, trying to use https://github.com/SaitoWu/grit_ext solve the encoding problem.

By Administrator on 2012-11-06T12:37:47 (imported from GitLab project)

Created by: rspeicher

https://github.com/balupton/history.js/issues/228 probably related.

By Administrator on 2012-11-06T17:01:22 (imported from GitLab project)

Created by: riyad

FYI: If I (left) click on a folder with a non-ascii name in the files view I get http://localhost:3000/gitlab/tree/non-ascii/test%20%C3%83%C2%A4%C3%83%C2%B6%C3%83%C2%BC If I open it in a new tab (i.e. middle click) I get http://localhost:3000/gitlab/tree/non-ascii/test%20%C3%A4%C3%B6%C3%BC

It should actually always be like the 2nd one.

By Administrator on 2012-11-06T17:11:15 (imported from GitLab project)

Created by: riyad

@SaitoWu would grit_ext solve both path and content encoding issues? If so, you are my hero. :)

By Administrator on 2012-11-06T19:05:54 (imported from GitLab project)

Created by: SaitoWu

@riyad Yeap, It will solve Git's 4 basic objects encoding problem. ( blob tree commit tag.

I mean will, need some time. :-)

gitlab and other app which use grit_ext will not need to care the encoding problem.

By Administrator on 2012-11-07T02:17:04 (imported from GitLab project)

Created by: SaitoWu

Why we need to handle many and many encoding problem and github not, Its because github is running on MRI 1.8.

And Grit is design for MRI 1.8, not for 1.9. Its the biggest different between we and github.

By Administrator on 2012-11-07T02:33:51 (imported from GitLab project)