From: "Jean-Baptiste Quenot" <jbq@caraldi.com>
To: git@vger.kernel.org
Subject: Using gitk over the network
Date: Wed, 19 Mar 2008 15:31:14 +0100 [thread overview]
Message-ID: <ae63f8b50803190731h49e224cby33344f8737f83718@mail.gmail.com> (raw)
Hi there,
I'm using gitk through an SSH-tunnelled X11 connection. Once loaded,
the GUI is usable on a DSL connection, but the problem is that gitk
loads the whole commit history, not only the commits that will fit on
screen. It can take up to a minute with our repository for the GUI to
be ready, especially when visualizing all branches.
I thought I'd let you know, in the case there is the possibility to
have some sort of progressive loading in the future. Compared to
gitk, git-gui works fine in this environment.
NOTE: I discovered tig today on this very mailing-list, and I admit
it's fulfilling part of our usecase, but maybe there are some people
in my team that are reluctant to text-based interfaces, who knows.
Cheers,
--
Jean-Baptiste Quenot
http://caraldi.com/jbq/blog/
reply other threads:[~2008-03-19 20:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae63f8b50803190731h49e224cby33344f8737f83718@mail.gmail.com \
--to=jbq@caraldi.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).