From: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2026, #07)
Date: Wed, 21 Jan 2026 18:03:06 -0300 [thread overview]
Message-ID: <69F44B0F-0780-4635-8685-704732FC4106@gmail.com> (raw)
In-Reply-To: <xmqq5x8uu6yk.fsf@gitster.g>
Hi, Junio
> "git repo info" learns "--keys" action to list known keys.
>
> Will merge to 'next'?
> source: <20260119210932.68893-1-lucasseikioshiro@gmail.com>
Not yet. The last review by Patrick made me rethink the entire
series and I still need to iterate a little more on it.
next prev parent reply other threads:[~2026-01-21 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 19:00 What's cooking in git.git (Jan 2026, #07) Junio C Hamano
2026-01-21 21:03 ` Lucas Seiki Oshiro [this message]
2026-01-21 21:08 ` Junio C Hamano
2026-01-22 0:59 ` Lorenzo Pegorari
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=69F44B0F-0780-4635-8685-704732FC4106@gmail.com \
--to=lucasseikioshiro@gmail.com \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox