From: Jonathan Tan <jonathantanmy@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2017, #07; Sat, 24)
Date: Mon, 26 Jun 2017 09:55:30 -0700 [thread overview]
Message-ID: <20170626095530.49c82646@twelve2.svl.corp.google.com> (raw)
In-Reply-To: <xmqq4lv57ypx.fsf@gitster.mtv.corp.google.com>
On Sat, 24 Jun 2017 16:25:13 -0700
Junio C Hamano <gitster@pobox.com> wrote:
> * jt/unify-object-info (2017-06-21) 8 commits
> - sha1_file: refactor has_sha1_file_with_flags
> - sha1_file: do not access pack if unneeded
> - sha1_file: improve sha1_object_info_extended
> - sha1_file: refactor read_object
> - sha1_file: move delta base cache code up
> - sha1_file: rename LOOKUP_REPLACE_OBJECT
> - sha1_file: rename LOOKUP_UNKNOWN_OBJECT
> - sha1_file: teach packed_object_info about typename
>
> Code clean-ups.
>
> Looked sensible to me. Any further comments?
> cf. <20170624124522.p2dnwdah75e4ngya@sigill.intra.peff.net>
In a reply that I just sent out [1], I suggested "sha1_file: support
more flags in object info query" to replace "sha1_file: improve
sha1_object_info_extended" (the 6th patch from the bottom). If you are
OK with that commit message title, and if you prefer not to make the
change locally yourself, I can send out a reroll with the updated commit
message title.
[1] https://public-inbox.org/git/CAGf8dgJ8C0chOxZo5CPt56225XGBgrjaGy8HDAST+0-USfW6mA@mail.gmail.com/
prev parent reply other threads:[~2017-06-26 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 23:25 What's cooking in git.git (Jun 2017, #07; Sat, 24) Junio C Hamano
2017-06-26 8:29 ` Lars Schneider
2017-06-26 9:44 ` Ævar Arnfjörð Bjarmason
2017-06-26 9:54 ` Lars Schneider
2017-06-26 15:49 ` Junio C Hamano
2017-06-26 16:55 ` Jonathan Tan [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=20170626095530.49c82646@twelve2.svl.corp.google.com \
--to=jonathantanmy@google.com \
--cc=git@vger.kernel.org \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox