All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: mr/bisect-in-c-3, was Re: What's cooking in git.git (Oct 2020, #03; Mon, 19)
Date: Wed, 21 Oct 2020 13:45:22 -0700	[thread overview]
Message-ID: <xmqq1rhr71gd.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <xmqq5z7371i2.fsf@gitster.c.googlers.com> (Junio C. Hamano's message of "Wed, 21 Oct 2020 13:44:21 -0700")

Junio C Hamano <gitster@pobox.com> writes:

>> It has been reviewed _quite_ a couple of times over the course of 9
>> iterations, and I think it is ready now.
>
> Oh, numbers I can count.  I wanted to hear "yes, all previously
> known issues have been addressed" from those who did read everything
> in it and gave their feedback.
>
> Do you want to give your "reviewed-by" now?

Ah, I should have looked again.  Yes, these look good (and the
sign-off chain ends with your reviewed-by already).

Thanks.

  reply	other threads:[~2020-10-21 20:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 18:13 What's cooking in git.git (Oct 2020, #03; Mon, 19) Junio C Hamano
2020-10-19 18:21 ` Eric Sunshine
2020-10-20 22:59   ` Junio C Hamano
2020-10-20 19:17 ` Preparing to rewind 'next' Junio C Hamano
2020-10-20 19:37   ` Matheus Tavares Bernardino
2020-10-21 14:48 ` mr/bisect-in-c-3, was Re: What's cooking in git.git (Oct 2020, #03; Mon, 19) Johannes Schindelin
2020-10-21 20:44   ` Junio C Hamano
2020-10-21 20:45     ` Junio C Hamano [this message]
2020-10-22 13:16     ` Johannes Schindelin
2020-10-23  8:02 ` Jeff King
2020-10-23 15:27   ` Junio C Hamano
2020-10-23 19:17   ` Elijah Newren
2020-10-27  8:39     ` Jeff King
2020-10-23 14:39 ` ak/corrected-commit-date, was " Jakub Narębski
2020-10-23 16:03   ` Junio C Hamano

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=xmqq1rhr71gd.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.