From: Junio C Hamano <gitster@pobox•com>
To: Santiago Torres <santiago@nyu•edu>
Cc: git@vger•kernel.org, ramsay@ramsayjones•plus.com
Subject: Re: What's cooking in git.git (Apr 2016, #06; Thu, 21)
Date: Thu, 21 Apr 2016 16:20:07 -0700 [thread overview]
Message-ID: <xmqqfuuer1lk.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160421225116.GF1096@LykOS> (Santiago Torres's message of "Thu, 21 Apr 2016 18:51:16 -0400")
Santiago Torres <santiago@nyu•edu> writes:
> On Thu, Apr 21, 2016 at 03:20:39PM -0700, Junio C Hamano wrote:
>> * st/verify-tag (2016-04-19) 6 commits
>> - tag -v: verfy directly rather than exec-ing verify-tag
>> - verify-tag: move tag verification code to tag.c
>> - verify-tag: prepare verify_tag for libification
>> - verify-tag: update variable name and type
>> - t7030: test verifying multiple tags
>> - builtin/verify-tag.c: ignore SIGPIPE in gpg-interface
>>
>> Unify internal logic between "git tag -v" and "git verify-tag"
>> commands by making one directly call into the other.
>>
>> Will merge to 'next'.
>
> Hi Junio,
>
> Ramsay Jones[1] Suggested we dropped the extern qualifier on the
> declaration of verify-tag() in tag.c as it is causing a warning with
> sparse.
>
> Should I re-roll this before it's merged into next?
Yes please.
next prev parent reply other threads:[~2016-04-21 23:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 22:20 What's cooking in git.git (Apr 2016, #06; Thu, 21) Junio C Hamano
2016-04-21 22:32 ` Stefan Beller
2016-04-21 22:48 ` Pranit Bauva
2016-04-22 17:23 ` Junio C Hamano
2016-04-22 22:12 ` Junio C Hamano
2016-04-23 18:42 ` Pranit Bauva
2016-04-21 22:51 ` Santiago Torres
2016-04-21 23:20 ` Junio C Hamano [this message]
2016-04-22 4:42 ` Jeff King
2016-04-22 17:22 ` Junio C Hamano
2016-04-22 18:38 ` Jeff King
2016-04-22 5:01 ` Torsten Bögershausen
2016-04-22 17:23 ` Junio C Hamano
2016-04-22 14:04 ` Johannes Schindelin
2016-04-22 17:24 ` Junio C Hamano
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=xmqqfuuer1lk.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=ramsay@ramsayjones$(echo .)plus.com \
--cc=santiago@nyu$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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