From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Tan <jonathantanmy@google.com>,
Chen Xuewei via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Chen Xuewei <316403398@qq.com>
Subject: Re: [PATCH] fix: platform accordance while calculating murmur3
Date: Thu, 4 Jan 2024 13:27:48 -0500 [thread overview]
Message-ID: <ZZb4pN/zR12m93L4@nand.local> (raw)
In-Reply-To: <xmqq7ckp7ysl.fsf@gitster.g>
On Thu, Jan 04, 2024 at 10:12:42AM -0800, Junio C Hamano wrote:
> Jonathan and Taylor, isn't this what you two were working together
> on? How would we want to proceed?
They are indeed similar. I think that Jonathan and my series would
supersede this effort.
But I would appreciate if Chen took a look at the approach in that
series to make sure that we're all on the same page and that Jonathan
and I aren't missing anything.
Thanks,
Taylor
prev parent reply other threads:[~2024-01-04 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 13:56 [PATCH] fix: platform accordance while calculating murmur3 Chen Xuewei via GitGitGadget
2024-01-04 14:53 ` Taylor Blau
2024-01-04 18:12 ` Junio C Hamano
2024-01-04 18:27 ` Taylor Blau [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZZb4pN/zR12m93L4@nand.local \
--to=me@ttaylorr.com \
--cc=316403398@qq.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.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;
as well as URLs for NNTP newsgroup(s).