From: Fabian Stelzer <fs@gigacodes.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2021, #04; Sun, 14)
Date: Mon, 15 Nov 2021 21:00:11 +0100 [thread overview]
Message-ID: <20211115200011.yr6wmyzmdyoaf6d7@fs> (raw)
In-Reply-To: <xmqqv90tfhh2.fsf@gitster.g>
On 15.11.2021 09:37, Junio C Hamano wrote:
>
>* fs/ssh-signing-key-lifetime (2021-10-27) 8 commits
> - ssh signing: make fmt-merge-msg consider key lifetime
> - ssh signing: make verify-tag consider key lifetime
> - ssh signing: make git log verify key lifetime
> - ssh signing: make verify-commit consider key lifetime
> - ssh signing: add key lifetime test prereqs
> - ssh signing: use sigc struct to pass payload
> - Merge branch 'fs/ssh-signing-fix' into fs/ssh-signing-key-lifetime
> - Merge branch 'fs/ssh-signing' into fs/ssh-signing-key-lifetime
>
> Extend the signing of objects with SSH keys and learn to pay
> attention to the key validity time range when verifying.
>
> Will merge to 'next'?
>
Please wait. I'll send a reroll shortly that i was holding back until
the release. Just some minor changes from the last review round and
improved test prereq to make sure ssh-keygen is working as we expect
like we spoke about in the other threads.
prev parent reply other threads:[~2021-11-16 0:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 17:37 What's cooking in git.git (Nov 2021, #04; Sun, 14) Junio C Hamano
2021-11-15 19:30 ` ab/mark-leak-free-tests-even-more (was: What's cooking in git.git (Nov 2021, #04; Sun, 14)) Ævar Arnfjörð Bjarmason
2021-11-15 22:16 ` Elijah Newren
2021-11-15 19:35 ` ab/only-single-progress-at-once " Ævar Arnfjörð Bjarmason
2021-11-15 19:37 ` ab/refs-errno-cleanup + hn/reftable " Ævar Arnfjörð Bjarmason
2021-11-15 20:00 ` Fabian Stelzer [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
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=20211115200011.yr6wmyzmdyoaf6d7@fs \
--to=fs@gigacodes.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).