From: Junio C Hamano <gitster@pobox.com>
To: Santiago Torres <santiago@nyu.edu>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2016, #03; Tue, 11)
Date: Tue, 18 Oct 2016 08:53:44 -0700 [thread overview]
Message-ID: <xmqqtwc9r6uv.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20161018133518.hwbv3gbeddjjfvcz@LykOS.localdomain> (Santiago Torres's message of "Tue, 18 Oct 2016 09:35:18 -0400")
Santiago Torres <santiago@nyu.edu> writes:
>> * 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.
next prev parent reply other threads:[~2016-10-18 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 21:06 What's cooking in git.git (Oct 2016, #03; Tue, 11) Junio C Hamano
2016-10-11 21:39 ` Stefan Beller
2016-10-11 21:39 ` Stefan Beller
2016-10-11 21:45 ` Junio C Hamano
2016-10-13 12:40 ` Johannes Schindelin
2016-10-14 16:10 ` Junio C Hamano
2016-10-16 8:31 ` Johannes Schindelin
2016-10-17 17:03 ` Junio C Hamano
2016-10-18 11:33 ` Johannes Schindelin
2016-10-18 13:35 ` Santiago Torres
2016-10-18 15:53 ` Junio C Hamano [this message]
2016-10-19 9:23 ` Jeff King
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=xmqqtwc9r6uv.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=santiago@nyu.edu \
/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).