From: Stefan Beller <sbeller@google.com>
To: Markus Hitter <mah@jump-ing.de>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
Paul Mackerras <paulus@ozlabs.org>
Subject: Re: Resend: Gitk: memory consumption improvements
Date: Fri, 9 Dec 2016 09:57:01 -0800 [thread overview]
Message-ID: <CAGZ79ka4TRXW7-YY8hqvYz_NJ+dZxtwY6KDSOJ+0cZF4i-J+fA@mail.gmail.com> (raw)
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:
>
> 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
next prev parent reply other threads:[~2016-12-09 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 11:51 Resend: Gitk: memory consumption improvements Markus Hitter
2016-12-09 17:57 ` Stefan Beller [this message]
2016-12-10 18:23 ` Markus Hitter
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=CAGZ79ka4TRXW7-YY8hqvYz_NJ+dZxtwY6KDSOJ+0cZF4i-J+fA@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=mah@jump-ing.de \
--cc=paulus@ozlabs.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).