git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Han-Wen Nienhuys <hanwen@google.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	git <git@vger.kernel.org>, "Elijah Newren" <newren@gmail.com>,
	"Jeff King" <peff@peff.net>, "Taylor Blau" <me@ttaylorr.com>,
	"René Scharfe" <l.s.r@web.de>
Subject: Re: What's cooking in git.git (Mar 2021, #03; Wed, 10)
Date: Thu, 11 Mar 2021 10:12:05 -0800	[thread overview]
Message-ID: <xmqq35x1ef0q.fsf@gitster.g> (raw)
In-Reply-To: <CAFQ2z_NL1NYunAKwGGF2eK4hMS11gz_4VUw1rhd2rmPw60OZ9Q@mail.gmail.com> (Han-Wen Nienhuys's message of "Thu, 11 Mar 2021 14:01:27 +0100")

Han-Wen Nienhuys <hanwen@google.com> writes:

> However, the primary reason nothing has changed is that I posted a
> large round of updates early December, in response to reviews from
> Google's git team, and I haven't gotten any code review or other type
> of feedback since (except your one message about the errno side band)
>
> Is there anything I should do to get this moving again?

Unfortunately there aren't many effective things the patch authors
can do (other than making sure their series are easily digestible
and by begging X-<) when nobody is looking at their patches and
potential reviewers and those who may show interest in the series
are running around producing their own changes instead of giving
reviews, both positive and negative.

I try to chip in with my own reviewing time but I am only a single
person, so help from others are required.

Thanks.


  reply	other threads:[~2021-03-11 18:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11  3:01 What's cooking in git.git (Mar 2021, #03; Wed, 10) Junio C Hamano
2021-03-11  4:49 ` Elijah Newren
2021-03-11  6:08   ` Junio C Hamano
2021-03-11  5:20 ` ZheNing Hu
2021-03-11  5:28   ` Junio C Hamano
2021-03-11  6:18     ` ZheNing Hu
2021-03-11 11:44 ` Ævar Arnfjörð Bjarmason
2021-03-11 13:01   ` Han-Wen Nienhuys
2021-03-11 18:12     ` Junio C Hamano [this message]
2021-03-11 16:17   ` Elijah Newren
2021-03-11 18:27   ` Junio C Hamano
2021-03-11 19:17     ` Jeff King
2021-03-12  7:10     ` Junio C Hamano
2021-03-11 19:13   ` René Scharfe.

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=xmqq35x1ef0q.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=hanwen@google.com \
    --cc=l.s.r@web.de \
    --cc=me@ttaylorr.com \
    --cc=newren@gmail.com \
    --cc=peff@peff.net \
    /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).