From: "René Scharfe" <l.s.r@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2017, #04; Tue, 14)
Date: Wed, 15 Feb 2017 17:13:44 +0100 [thread overview]
Message-ID: <df42ec26-d1b1-e31b-b16d-554441a335f0@web.de> (raw)
In-Reply-To: <xmqq60kc750b.fsf@gitster.mtv.corp.google.com>
Am 14.02.2017 um 23:59 schrieb Junio C Hamano:
> * rs/ls-files-partial-optim (2017-02-13) 2 commits
> - ls-files: move only kept cache entries in prune_cache()
> - ls-files: pass prefix length explicitly to prune_cache()
>
> "ls-files" run with pathspec has been micro-optimized to avoid one
> extra call to memmove().
Nit: The number of memmove(3) calls stays the same, but the number of
bytes that are moved is reduced.
René
next prev parent reply other threads:[~2017-02-15 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 22:59 What's cooking in git.git (Feb 2017, #04; Tue, 14) Junio C Hamano
2017-02-15 16:13 ` René Scharfe [this message]
2017-02-16 17:10 ` Junio C Hamano
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=df42ec26-d1b1-e31b-b16d-554441a335f0@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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