Re: Resend: Gitk: memory consumption improvements

From: Stefan Beller <sbeller@google.com>
Date: Dec 9, 2016, 17:57 UTC
Message-ID: <CAGZ79ka4TRXW7-YY8hqvYz_NJ+dZxtwY6KDSOJ+0cZF4i-J+fA@mail.gmail.com>
In-Reply-To: <d10d2b12-4ef1-61e9-0b3c-89aa41c9eeff@jump-ing.de>

On Fri, Dec 9, 2016 at 3:51 AM, Markus Hitter <mah@jump-ing.de> wrote:

Show 9 quoted lines

>
> It's a month now since I sent three patches to this list for reducing memory consumption of Gitk considerably:
>
> https://public-inbox.org/git/de7cd593-0c10-4e93-1681-7e123504f5d5@jump-ing.de/
> https://public-inbox.org/git/e09a5309-351d-d246-d272-f527f50ad444@jump-ing.de/
> https://public-inbox.org/git/8e1c5923-d2a6-bc77-97ab-3f154b41d2ea@jump-ing.de/
> https://public-inbox.org/git/2cb7f76f-0004-a5b6-79f1-9bb4f979cf14@jump-ing.de/
>
> Everybody cheered, but apparently nobody picked these patches up and applied them to either the Git or Gitk repository. They don't appear in the regular "what's cooking" post either.

The "What's cooking" email is done by Junio (the Git maintainer) describing the development of Git, whereas gitk is maintained by Paul if I understand correctly.

If you look at the Git history, the changes to gitk-git/ always come in via a merge/pull from Paul.

>
> Anything missing? I'd like to put a 'done' checkmark behind this.
>

I'd love to see those patches in use here (via a regular upstream update).

So I guess the way to go for you is to keep bugging Paul for an ack?

Thanks, Stefan