From: Jeff King <peff@peff.net>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Johannes Sixt <j6t@kdbg.org>,
Aaron Schrab <aaron@schrab.com>,
Clemens Buchacher <drizzd@aon.at>,
David Michael Barr <b@rr-dav.id.au>,
Florian Achleitner <florian.achleitner.2.6.31@gmail.com>
Subject: Re: [PATCH v3 2/2] transport-helper: check if remote helper is alive
Date: Mon, 8 Apr 2013 14:49:33 -0400 [thread overview]
Message-ID: <20130408184933.GA7337@sigill.intra.peff.net> (raw)
In-Reply-To: <CAMP44s2PJGJQBM86CGsA5BOn1RLi4mqNsq+d0oyY0jA=XHQGDA@mail.gmail.com>
On Mon, Apr 08, 2013 at 01:31:43PM -0500, Felipe Contreras wrote:
> > Reviewers have limited time allocated for each individual topic. To
> > an original patch with say 3 problems, the review may only point out
> > issues in 2 and suggest a concrete improvement for only 1 and that
> > is sufficient to suggest a reroll. That is not being unhelpful by
> > deliberately withholding 1 and half reviews in the initial round.
>
> I'm not talking about the time it took to come up with the criticism
> below, I'm talking about the comment regarding the commit message. If
> the commit message did indeed provide *zero* explanation, that's
> certainly something that should be immediately visible, no? It could
> have been mentioned six months ago.
I do not recall this series at all from six months ago. I reviewed a
series (with no version markers, nor any mention of the previous round)
posted on April 1st, and assumed it was a new series. I raised the same
issues there that I did in v3, though in less detail (because I had not
yet looked into it as thoroughly).
I searched the archive after reading this mail and found the original
series. Yes, it existed. I didn't review it. I guess I had something
more important to do that day.
But is all of this even important? If there are technical issues with
this series, does it matter when we find out about them? They still
deserve to be fixed, no? Yes, it is nice if things get reviewed
promptly, but the limited bandwidth and attention of reviewers is a fact
of life.
-Peff
next prev parent reply other threads:[~2013-04-08 18:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 7:45 [PATCH v3 0/2] run-command: new check_command helper Felipe Contreras
2013-04-07 7:45 ` [PATCH v3 1/2] run-command: add " Felipe Contreras
2013-04-07 17:47 ` Junio C Hamano
2013-04-07 17:52 ` Junio C Hamano
2013-04-07 7:45 ` [PATCH v3 2/2] transport-helper: check if remote helper is alive Felipe Contreras
2013-04-07 17:49 ` Junio C Hamano
2013-04-08 0:51 ` Jeff King
2013-04-08 2:03 ` Felipe Contreras
2013-04-08 2:33 ` Jeff King
2013-04-08 14:38 ` Felipe Contreras
2013-04-08 17:43 ` Junio C Hamano
2013-04-08 18:31 ` Felipe Contreras
2013-04-08 18:46 ` Junio C Hamano
2013-04-08 19:08 ` Felipe Contreras
2013-04-08 21:08 ` Junio C Hamano
2013-04-08 21:11 ` Jeff King
2013-04-08 21:21 ` Junio C Hamano
2013-04-08 18:49 ` Jeff King [this message]
2013-04-08 19:15 ` Jeff King
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=20130408184933.GA7337@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=aaron@schrab.com \
--cc=b@rr-dav.id.au \
--cc=drizzd@aon.at \
--cc=felipe.contreras@gmail.com \
--cc=florian.achleitner.2.6.31@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.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 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).