From: Junio C Hamano <gitster@pobox•com>
To: Santiago Torres <santiago@nyu•edu>
Cc: git@vger•kernel.org, peff@peff•net, sunshine@sunshineco•com,
walters@verbum•org
Subject: Re: [PATCH v3 0/5] Add --format to tag verification
Date: Mon, 03 Oct 2016 13:58:55 -0700 [thread overview]
Message-ID: <xmqqshsd5euo.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20161003144901.4yainza537g5bujz@LykOS.localdomain> (Santiago Torres's message of "Mon, 3 Oct 2016 10:49:03 -0400")
Santiago Torres <santiago@nyu•edu> writes:
> Hi, Junio.
>> I however notice that there is no new tests to protect these two new
>> features from future breakages. Perhaps you want to add some in
>> [6/5]?
>
> I'll be working on this. I spent some time looking around for example
> tests for format. Are there any that I should pay special attention to?
> (I'm looking at t7004 mostly right now).
By the way, running t7030 seems to reveal a segfault introduced by
this 5-patch series.
prev parent reply other threads:[~2016-10-03 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 22:18 [PATCH v3 0/5] Add --format to tag verification santiago
2016-09-30 22:18 ` [PATCH v3 1/5] gpg-interface, tag: add GPG_VERIFY_QUIET flag santiago
2016-09-30 22:18 ` [PATCH v3 2/5] ref-filter: add function to print single ref_array_item santiago
2016-09-30 23:12 ` Jakub Narębski
2016-10-01 1:33 ` Junio C Hamano
2016-09-30 22:18 ` [PATCH v3 3/5] tag: add format specifier to gpg_verify_tag santiago
2016-09-30 22:18 ` [PATCH v3 4/5] builtin/verify-tag: add --format to verify-tag santiago
2016-09-30 22:18 ` [PATCH v3 5/5] builtin/tag: add --format argument for tag -v santiago
2016-09-30 23:28 ` [PATCH v3 0/5] Add --format to tag verification Junio C Hamano
2016-10-03 14:49 ` Santiago Torres
2016-10-03 20:58 ` Junio C Hamano [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=xmqqshsd5euo.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=peff@peff$(echo .)net \
--cc=santiago@nyu$(echo .)edu \
--cc=sunshine@sunshineco$(echo .)com \
--cc=walters@verbum$(echo .)org \
/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