From: "Оля Тележная" <olyatelezhnaya@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jul 2018, #02; Wed, 18)
Date: Thu, 19 Jul 2018 09:10:08 +0300 [thread overview]
Message-ID: <CAL21BmmALPba5NEH-sq42mX5xS-CAPoupjftw390XWjJeQXoDA@mail.gmail.com> (raw)
In-Reply-To: <xmqqtvowi4l3.fsf@gitster-ct.c.googlers.com>
> * ot/ref-filter-object-info (2018-07-17) 5 commits
> - ref-filter: use oid_object_info() to get object
> - ref-filter: merge get_obj and get_object
> - ref-filter: initialize eaten variable
> - ref-filter: fill empty fields with empty values
> - ref-filter: add info_source to valid_atom
>
> A few atoms like %(objecttype) and %(objectsize) in the format
> specifier of "for-each-ref --format=<format>" can be filled without
> getting the full contents of the object, but just with the object
> header. These cases have been optimzied by calling
> oid_object_info() API.
>
> What's the doneness of this one?
>
I fixed all known issues, I hope we can move forward with it.
Thank you!
next prev parent reply other threads:[~2018-07-19 6:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 22:03 What's cooking in git.git (Jul 2018, #02; Wed, 18) Junio C Hamano
2018-07-18 23:41 ` Stefan Beller
2018-07-19 16:33 ` Junio C Hamano
2018-07-19 6:10 ` Оля Тележная [this message]
2018-07-19 8:48 ` Eric Sunshine
2018-07-19 16:36 ` Junio C Hamano
2018-07-19 17:10 ` Elijah Newren
2018-07-20 13:42 ` ds/multi-pack-index (was Re: What's cooking in git.git (Jul 2018, #02; Wed, 18)) Derrick Stolee
2018-07-20 16:09 ` Junio C Hamano
2018-07-20 16:28 ` Derrick Stolee
2018-07-20 17:48 ` ag/rebase-i-in-c, was Re: What's cooking in git.git (Jul 2018, #02; Wed, 18) Alban Gruin
2018-07-23 18:21 ` Jonathan Tan
2018-07-24 19:31 ` Junio C Hamano
2018-07-24 19:38 ` Brandon Williams
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=CAL21BmmALPba5NEH-sq42mX5xS-CAPoupjftw390XWjJeQXoDA@mail.gmail.com \
--to=olyatelezhnaya@gmail.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.
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).