From: Jeff Hostetler <git@jeffhostetler.com>
To: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 0/1] Optimize run_diff_files()' rename detection
Date: Mon, 10 Jun 2019 10:43:36 -0400 [thread overview]
Message-ID: <bd404b8b-7747-3e29-8d14-ed2f04d12292@jeffhostetler.com> (raw)
In-Reply-To: <pull.142.git.gitgitgadget@gmail.com>
On 6/8/2019 10:42 AM, Johannes Schindelin via GitGitGadget wrote:
> Just another patch from Git for Windows' branch thicket...
>
> Jeff Hostetler (1):
> diffcore-rename: speed up register_rename_src
>
> diffcore-rename.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
>
> base-commit: 8104ec994ea3849a968b4667d072fedd1e688642
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-142%2Fdscho%2Fregister_rename_src-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-142/dscho/register_rename_src-v1
> Pull-Request: https://github.com/gitgitgadget/git/pull/142
>
For the sake of full disclosure, we added this patch
to Git for Windows in December 2016.
It was discussed on the mailing list in April 2017 [1] but
it was shelved for various reasons.
Let me put this one on hold while I dig up my notes from 2016
and re-review of the original mailing list suggestions and
see where I want to take this patch going forward.
Jeff
[1]
https://public-inbox.org/git/20170418194421.22453-1-git@jeffhostetler.com/
prev parent reply other threads:[~2019-06-10 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 14:42 [PATCH 0/1] Optimize run_diff_files()' rename detection Johannes Schindelin via GitGitGadget
2019-06-08 14:42 ` [PATCH 1/1] diffcore-rename: speed up register_rename_src Jeff Hostetler via GitGitGadget
2019-06-08 22:27 ` René Scharfe
2019-06-10 14:23 ` Jeff Hostetler
2019-06-10 12:26 ` SZEDER Gábor
2019-06-10 14:55 ` Jeff Hostetler
2019-06-10 14:43 ` Jeff Hostetler [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bd404b8b-7747-3e29-8d14-ed2f04d12292@jeffhostetler.com \
--to=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).