From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Andreas Krey <a.krey@gmx.de>, John Keeping <john@keeping.me.uk>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: best practices against long git rebase times?
Date: Mon, 07 Dec 2015 16:18:29 -0800 [thread overview]
Message-ID: <xmqqio49lrmy.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20151207225957.GB3785@sigill.intra.peff.net> (Jeff King's message of "Mon, 7 Dec 2015 17:59:57 -0500")
Jeff King <peff@peff.net> writes:
> I think you missed John's earlier response which gave several pointers
> to such caching schemes. :)
Yeah, you're right.
>
> I used to run with patch-id-caching in my personal fork (I frequently
> use "git log --cherry-mark" to see what has made it upstream), but I
> haven't for a while. It did make a big difference in speed, but I never
> resolved the corner cases around cache invalidation.
>
> -Peff
next prev parent reply other threads:[~2015-12-08 0:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 15:05 best practices against long git rebase times? Andreas Krey
2015-12-04 15:31 ` John Keeping
2015-12-06 16:43 ` Andreas Krey
2015-12-07 21:02 ` Jeff King
2015-12-07 22:56 ` Junio C Hamano
2015-12-07 22:59 ` Jeff King
2015-12-08 0:18 ` Junio C Hamano [this message]
2015-12-08 17:45 ` Christian Couder
2015-12-04 17:09 ` demerphq
2015-12-04 17:28 ` John Keeping
2015-12-04 17:33 ` demerphq
2015-12-04 18:10 ` Stefan Beller
2015-12-06 16:40 ` Andreas Krey
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=xmqqio49lrmy.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=a.krey@gmx.de \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.