Re: What's cooking in git.git (Oct 2016, #03; Tue, 11)

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 18, 2016, 15:53 UTC
Message-ID: <xmqqtwc9r6uv.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <20161018133518.hwbv3gbeddjjfvcz@LykOS.localdomain>

Santiago Torres <santiago@nyu.edu> writes:

Show 16 quoted lines

>> * st/verify-tag (2016-10-10) 7 commits
>>  - t/t7004-tag: Add --format specifier tests
>>  - t/t7030-verify-tag: Add --format specifier tests
>>  - builtin/tag: add --format argument for tag -v
>>  - builtin/verify-tag: add --format to verify-tag
>>  - tag: add format specifier to gpg_verify_tag
>>  - ref-filter: add function to print single ref_array_item
>>  - gpg-interface, tag: add GPG_VERIFY_QUIET flag
>> 
>>  "git tag" and "git verify-tag" learned to put GPG verification
>>  status in their "--format=<placeholders>" output format.
>> 
>>  Is this ready for 'next'?
>
> Hi, I saw this on the previous "what's cooking." Is there anything I
> need to do on my side to make sure this is ready for next?

Posting this exact message to the list would be an excellent way ;-).

Hopefully some competent reviewer comes and points me at a thread where s/he says the series was already reviewed and in good shape soonish, and your message may be a good trigger to make it happen.