From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org, "Jeff King" <peff@peff.net>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: [PATCH v3 00/20] object_id part 7
Date: Fri, 31 Mar 2017 08:46:44 -0700 [thread overview]
Message-ID: <xmqqa8811maj.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170331014001.953484-1-sandals@crustytoothpaste.net> (brian m. carlson's message of "Fri, 31 Mar 2017 01:39:41 +0000")
Thanks for these patches. I didn't see anything questionable in
them (except a very minor thing I sent comments on separately).
Will replace. Thanks.
prev parent reply other threads:[~2017-03-31 15:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 1:39 [PATCH v3 00/20] object_id part 7 brian m. carlson
2017-03-31 1:39 ` [PATCH v3 01/20] Define new hash-size constants for allocating memory brian m. carlson
2017-03-31 1:39 ` [PATCH v3 02/20] Convert GIT_SHA1_HEXSZ used for allocation to GIT_MAX_HEXSZ brian m. carlson
2017-03-31 1:39 ` [PATCH v3 03/20] Convert GIT_SHA1_RAWSZ used for allocation to GIT_MAX_RAWSZ brian m. carlson
2017-03-31 1:39 ` [PATCH v3 04/20] builtin/diff: convert to struct object_id brian m. carlson
2017-03-31 1:39 ` [PATCH v3 05/20] builtin/pull: convert portions " brian m. carlson
2017-03-31 1:39 ` [PATCH v3 06/20] builtin/receive-pack: " brian m. carlson
2017-07-15 18:33 ` René Scharfe
2017-03-31 1:39 ` [PATCH v3 07/20] fsck: convert init_skiplist " brian m. carlson
2017-03-31 1:39 ` [PATCH v3 08/20] parse-options-cb: convert sha1_array_append caller " brian m. carlson
2017-03-31 1:39 ` [PATCH v3 09/20] test-sha1-array: convert most code " brian m. carlson
2017-03-31 1:39 ` [PATCH v3 10/20] sha1_name: convert struct disambiguate_state to object_id brian m. carlson
2017-03-31 1:39 ` [PATCH v3 11/20] sha1_name: convert disambiguate_hint_fn to take object_id brian m. carlson
2017-03-31 1:39 ` [PATCH v3 12/20] submodule: convert check_for_new_submodule_commits to object_id brian m. carlson
2017-03-31 1:39 ` [PATCH v3 13/20] builtin/pull: convert to struct object_id brian m. carlson
2017-03-31 1:39 ` [PATCH v3 14/20] sha1-array: convert internal storage for struct sha1_array to object_id brian m. carlson
2017-03-31 15:42 ` Junio C Hamano
2017-03-31 1:39 ` [PATCH v3 15/20] Make sha1_array_append take a struct object_id * brian m. carlson
2017-03-31 1:39 ` [PATCH v3 16/20] Convert remaining callers of sha1_array_lookup to object_id brian m. carlson
2017-03-31 1:39 ` [PATCH v3 17/20] Convert sha1_array_lookup to take struct object_id brian m. carlson
2017-03-31 1:39 ` [PATCH v3 18/20] Convert sha1_array_for_each_unique and for_each_abbrev to object_id brian m. carlson
2017-03-31 1:40 ` [PATCH v3 19/20] Rename sha1_array to oid_array brian m. carlson
2017-03-31 1:40 ` [PATCH v3 20/20] Documentation: update and rename api-sha1-array.txt brian m. carlson
2017-03-31 15:46 ` 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
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=xmqqa8811maj.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.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.
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).