From: Jeff King <peff@peff.net>
To: Santiago Torres Arias <santiago@nyu.edu>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2019, #04; Mon, 22)
Date: Mon, 22 Apr 2019 11:28:42 -0400 [thread overview]
Message-ID: <20190422152842.GC1633@sigill.intra.peff.net> (raw)
In-Reply-To: <20190422145237.v5xjelebyjxb3uko@LykOS.localdomain>
On Mon, Apr 22, 2019 at 10:52:38AM -0400, Santiago Torres Arias wrote:
> On Mon, Apr 22, 2019 at 03:10:30PM +0900, Junio C Hamano wrote:
> > Here are the topics that have been cooking. Commits prefixed with
> > '-' are only in 'pu' (proposed updates) while commits prefixed with
> > '+' are in 'next'. The ones marked with '.' do not appear in any of
> > the integration branches, but I am still holding onto them.
> >
> > You can find the changes described here in the integration branches
> > of the repositories listed at
>
> Hi,
>
> This is the second what's cooking that's gone by without mention of the
> RFC patch regarding verify_tag[1]. Is this due to lack of interest or is
> this an error on my side (f.e., did I forget to send something?).
I think anything marked "RFC" that does not get much discussion is
likely to get overlooked by a busy maintainer. :) I had your patch on my
todo list, and I just wrote up some comments in that thread.
-Peff
next prev parent reply other threads:[~2019-04-22 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 6:10 What's cooking in git.git (Apr 2019, #04; Mon, 22) Junio C Hamano
2019-04-22 14:52 ` Santiago Torres Arias
2019-04-22 15:28 ` Jeff King [this message]
2019-04-22 15:43 ` Santiago Torres Arias
2019-04-22 17:51 ` jt/fetch-cdn-offload (was What's cooking in git.git (Apr 2019, #04; Mon, 22)) Jonathan Tan
2019-04-22 18:33 ` Ramsay Jones
2019-04-23 5:34 ` Jeff King
2019-04-23 6:52 ` Christian Couder
2019-05-06 19:19 ` Jonathan Tan
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=20190422152842.GC1633@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=santiago@nyu.edu \
/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;
as well as URLs for NNTP newsgroup(s).