Re: Thoughts on gitk's memory footprint over linux-2.6.git
- From
Martin Langhoff <martin.langhoff@gmail.com>
- Date
- Sep 26, 2011, 22:07 UTC
- Message-ID
- <CACPiFCJvg4X7yL0FUYEtB4U4cabyczrHGDapTgLncFCoDF1EEQ@mail.gmail.com>
- In-Reply-To
- <CABPp-BHo5qKQVFRzFpoyt6dZZ3=UqVAtSjVy0uRDWnA+ASsBPw@mail.gmail.com>
On Mon, Sep 26, 2011 at 6:02 PM, Elijah Newren <newren@gmail.com> wrote:
> If you only want to look at a couple commits, you could tell gitk that: > gitk -N
I know I can -- I've done my bit of git hacking but it was long ago so if you use your -N parameter you won't see it ;-)
I argue that -n 10000 should be the default -- most of the time you open git to see recent commits, not that 2.6.12-rc3 commit. Of course, it cannot actually be the default, because currently there's no way to scroll past that limiter.
It's a hard limit, and that's not useful.
Now, git internally is very smart about using sliding windows over large datasets. The porcelain tools don't try to be so smart, but we're at a point where, as a user, I really wish gitk had some of that magic.
cheers,
m
-- martin.langhoff@gmail.com martin@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff