Sytse, I don't really know if the issue is the same, because I'm pretty new to gitlab and its internals (but I have a few year of experience in managing "big" git repository from command line)
I was wondering if there's a way to "simplify" gitlab blame view. Let's say: if the call timed out after the defined timeout don't only show a 502 error but also allow the use to have a "faster" (even in probably not so beautiful) view of the required page. I don't really know why that blame requires such a long time, probably to fetch additional information from all the blame references, and I don't really know if it's easier or not to have a "faster/lightweight" blame functionality, but, IMHO, this will be a real plus of gitlab, allowing to use it on less powerful servers and let it having a larger audience. Best Regards and thanks in advance for any clue in how to solve/improve (or help solving/improve) this issue. Andrea Il giorno lunedì 2 marzo 2015 22:36:06 UTC+1, sytse ha scritto: > > This issue (or a similar one) is being discussed in > https://gitlab.com/gitlab-org/gitlab-ce/issues/859#note_889474 > > Best regards, > Sytse Sijbrandij > CEO GitLab B.V. > > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/d1adca03-9e95-4cfe-a542-73ea84e37342%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
