From: Junio C Hamano <gitster@pobox.com>
To: Ben Peart <peartben@gmail.com>
Cc: Ben Peart <benpeart@microsoft.com>,
git@vger.kernel.org, pclouds@gmail.com, blees@dcon.de
Subject: Re: [PATCH v1] Fix bugs preventing adding updated cache entries to the name hash
Date: Thu, 15 Mar 2018 11:58:11 -0700 [thread overview]
Message-ID: <xmqqy3it414s.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <339cd7f7-9ca0-62cf-ea46-588be119eedd@gmail.com> (Ben Peart's message of "Thu, 15 Mar 2018 14:44:06 -0400")
Ben Peart <peartben@gmail.com> writes:
> This 2nd part of the patch was more for code cleanliness.
Thanks.
prev parent reply other threads:[~2018-03-15 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 15:25 [PATCH v1] Fix bugs preventing adding updated cache entries to the name hash Ben Peart
2018-03-15 17:58 ` Junio C Hamano
2018-03-15 18:44 ` Ben Peart
2018-03-15 18:58 ` Junio C Hamano [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=xmqqy3it414s.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=benpeart@microsoft.com \
--cc=blees@dcon.de \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peartben@gmail.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).