{"thread":{"id":"12757","subject":"Using gitk over the network","startedAt":"2008-03-19T14:31:14Z","lastAt":"2008-03-19T14:31:14Z","messageCount":1,"participants":["Jean-Baptiste Quenot"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"72394","messageId":"ae63f8b50803190731h49e224cby33344f8737f83718@mail.gmail.com","threadId":"12757","inReplyTo":null,"subject":"Using gitk over the network","fromName":"Jean-Baptiste Quenot","fromEmail":"jbq@caraldi.com","sentAt":"2008-03-19T14:31:14Z","receivedAt":"2008-03-19T14:31:14Z","isPatch":false,"sender":{"key":"jbq@caraldi.com","avatar":null},"body":"Hi there,\n\nI'm using gitk through an SSH-tunnelled X11 connection.  Once loaded,\nthe GUI is usable on a DSL connection, but the problem is that gitk\nloads the whole commit history, not only the commits that will fit on\nscreen.  It can take up to a minute with our repository for the GUI to\nbe ready, especially when visualizing all branches.\n\nI thought I'd let you know, in the case there is the possibility to\nhave some sort of progressive loading in the future.  Compared to\ngitk, git-gui works fine in this environment.\n\nNOTE: I discovered tig today on this very mailing-list, and I admit\nit's fulfilling part of our usecase, but maybe there are some people\nin my team that are reluctant to text-based interfaces, who knows.\n\nCheers,\n-- \nJean-Baptiste Quenot\nhttp://caraldi.com/jbq/blog/\n"}]}