From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Ramsay Jones <ramsay@ramsayjones.plus.com>,
git@vger.kernel.org, Alex <agrambot@gmail.com>
Subject: Re: [PATCH v2] gpg-interface: use more status letters
Date: Mon, 10 Oct 2016 10:58:31 -0700 [thread overview]
Message-ID: <xmqqtwckf5mg.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <8e496061-ce6c-450f-7c9e-785572d50b79@drmicha.warpmail.net> (Michael J. Gruber's message of "Mon, 10 Oct 2016 14:59:49 +0200")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> Sorry, this got "lost in vacation". Before that, I was looking for an
> easy way to test expired signatures, but gpg1 and gpg2 behave somewhat
> differently in that respect (2 does not allow to create already expired
> signatures).
>
> Is there anything I should or could do now?
I dunno. It's your itch.
You can say "I'll need more time to figure out the way to test what
I am not testing here, so do not merge it to 'next' yet".
You can also say "This is good enough for now, so go ahead and merge
it to 'next'; more detailed tests can be done as follow-up patches
if needed".
You can also say "Thinking about it again, there is no strong reason
why we need to differentiate EXPSIG and EXPKEYSIG, so don't do this
SQUASH and use my original one as-is".
I'd be happy with any of the above and there may be other ones I'd
be happy with that I haven't thought of ;-)
next prev parent reply other threads:[~2016-10-10 17:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 6:05 Request: Extra case for %G? format Alex
2016-09-26 11:53 ` Michael J Gruber
2016-09-26 17:18 ` Alex
2016-09-27 14:31 ` [PATCH] gpg-interface: use more status letters Michael J Gruber
2016-09-27 17:25 ` Junio C Hamano
2016-09-28 14:24 ` [PATCH v2] " Michael J Gruber
2016-09-28 15:10 ` Ramsay Jones
2016-09-28 19:59 ` Junio C Hamano
2016-09-28 21:09 ` Ramsay Jones
2016-09-30 9:41 ` Michael J Gruber
2016-09-30 16:16 ` Junio C Hamano
2016-10-06 21:43 ` Junio C Hamano
2016-10-10 12:59 ` Michael J Gruber
2016-10-10 17:58 ` Junio C Hamano [this message]
2016-10-12 13:04 ` [PATCH v3] " Michael J Gruber
2016-09-30 9:33 ` [PATCH v2] " Michael J Gruber
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=xmqqtwckf5mg.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=agrambot@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.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).