The linux-2.6 repository is huge, so using gitk on it does unfortunately
require a lot of memory (ideally 2 GiB or more). You can make things a
little bit better by unchecking Edit → Preferences → Display nearby
tags, and also by only using gitk on specific ranges of the history or
specific subtrees that you’re interested in (see the manpage).
linux-next is even huger, but actually the real problem there is that
linux-next gets rebased, so by running ‘git pull’ you are actually performing a
big merge operation (between today’s -next and yesterday’s -next) that you did
not want to perform. To update your checkout of linux-next, you should instead
use
git fetch
git reset --hard origin/master
It is hard to say whether any of these operations can be made more
efficient—Git is already orders of magnitude more efficient than other
version control systems. So without a particular description of the
inefficiencies, these problems can’t really be considered bugs in Git.
(I’m not saying it’s impossible to do better; just that we need
something more technically specific than “these operations are slow”.)
But I hope this is helpful anyway.
** Changed in: git-core (Ubuntu)
Status: New => Invalid
--
graphical nonresponsivness while "gitk" on linux kernel source
https://bugs.launchpad.net/bugs/585603
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
