From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 4/6] rerere: use strmap to store rerere directories
Date: Wed, 27 Jan 2021 22:38:31 -0800 [thread overview]
Message-ID: <xmqqzh0twopk.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <YBJXYMFu8dhOabDv@coredump.intra.peff.net> (Jeff King's message of "Thu, 28 Jan 2021 01:19:12 -0500")
Jeff King <peff@peff.net> writes:
> On Thu, Dec 03, 2020 at 11:28:14AM -0500, Jeff King wrote:
Curiously, the reference of the message points at the cover letter
of this series, and there is no mention of a message from early last
December.
I think this is good. These "conflict IDs" are not even object
names, so it would be strange to use "struct object_id" for them
(for that matter, packfile ids are not object names, either, but I
suspect we might use object_id there).
If there were a patch that can readily applied ;-)
next prev parent reply other threads:[~2021-01-28 6:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 6:12 [PATCH 0/6] convert hash_pos() to oid_pos() Jeff King
2021-01-28 6:12 ` [PATCH 1/6] commit_graft_pos(): take an oid instead of a bare hash Jeff King
2021-01-28 12:57 ` Derrick Stolee
2021-01-28 6:14 ` [PATCH 2/6] rerere: check dirname format while iterating rr_cache directory Jeff King
2021-01-28 6:16 ` [PATCH 3/6] rerere: tighten rr-cache dirname check Jeff King
2021-01-28 22:35 ` Taylor Blau
2021-01-28 6:19 ` [PATCH 4/6] rerere: use strmap to store rerere directories Jeff King
2021-01-28 6:34 ` Jeff King
2021-01-28 19:52 ` Junio C Hamano
2021-01-28 6:38 ` Junio C Hamano [this message]
2021-01-28 6:51 ` Jeff King
2021-01-28 6:19 ` [PATCH 5/6] hash_pos(): convert to oid_pos() Jeff King
2021-01-28 22:48 ` Taylor Blau
2021-01-29 1:18 ` Jeff King
2021-01-28 6:20 ` [PATCH 6/6] oid_pos(): access table through const pointers Jeff King
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=xmqqzh0twopk.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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 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).