From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Jeff King" <peff@peff.net>,
"René Scharfe" <l.s.r@web.de>
Subject: Re: What's cooking in git.git (Nov 2018, #06; Wed, 21)
Date: Wed, 21 Nov 2018 11:48:14 +0100 [thread overview]
Message-ID: <87muq2zoy9.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqlg5m7qlb.fsf@gitster-ct.c.googlers.com>
On Wed, Nov 21 2018, Junio C Hamano wrote:
> * jk/loose-object-cache (2018-11-13) 9 commits
> (merged to 'next' on 2018-11-18 at 276691a21b)
> + fetch-pack: drop custom loose object cache
> + sha1-file: use loose object cache for quick existence check
> + object-store: provide helpers for loose_objects_cache
> + sha1-file: use an object_directory for the main object dir
> + handle alternates paths the same as the main object dir
> + sha1_file_name(): overwrite buffer instead of appending
> + rename "alternate_object_database" to "object_directory"
> + submodule--helper: prefer strip_suffix() to ends_with()
> + fsck: do not reuse child_process structs
>
> Code clean-up with optimization for the codepath that checks
> (non-)existence of loose objects.
>
> Will cook in 'next'.
I think as noted in
https://public-inbox.org/git/e5148b8c-9a3a-5d2e-ac8c-3e536c0f2358@web.de/
that we should hold off the [89]/9 of this series due to the performance
regressions this introduces in some cases (while fixing other cases).
I hadn't had time to follow up on that, and figured it could wait until
post-2.20 for a re-roll.
next prev parent reply other threads:[~2018-11-21 10:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 9:00 What's cooking in git.git (Nov 2018, #06; Wed, 21) Junio C Hamano
2018-11-21 10:48 ` Ævar Arnfjörð Bjarmason [this message]
2018-11-22 17:53 ` Jeff King
2018-11-22 18:36 ` Ævar Arnfjörð Bjarmason
2018-11-24 12:09 ` Jeff King
2018-11-25 2:02 ` Junio C Hamano
2018-11-26 18:13 ` Jeff King
2018-11-24 2:11 ` Junio C Hamano
2018-11-24 12:06 ` Jeff King
2018-11-21 20:11 ` js/vsts-ci, was " Johannes Schindelin
2018-11-21 23:54 ` Stephen P. Smith
2018-11-22 1:06 ` Junio C Hamano
2018-11-22 2:08 ` Stephen P. Smith
2018-11-22 16:05 ` Linus Torvalds
2018-11-22 10:48 ` Ævar Arnfjörð Bjarmason
2018-11-26 21:57 ` Stefan Beller
2018-11-26 23:34 ` Junio C Hamano
2018-12-05 22:04 ` Matthew DeVore
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=87muq2zoy9.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
--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.