git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antoine Pelisse <apelisse@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jun 2013, #07; Thu, 20)
Date: Fri, 21 Jun 2013 19:32:45 +0200	[thread overview]
Message-ID: <CALWbr2xzozGkH23pYCj6XvW3nXF47YCEFGhy+-ivQRrW9FVOPg@mail.gmail.com> (raw)
In-Reply-To: <CALkWK0mUcJ1f0xP2w-fUFr-tMSKMX23_nmYQUYXw3zjw7Hm9GQ@mail.gmail.com>

On Fri, Jun 21, 2013 at 7:13 PM, Ramkumar Ramachandra
<artagnon@gmail.com> wrote:
> Junio C Hamano wrote:
>>> ...  I've noticed a significant decline in
>>> list-reviews in general: a lot of good code on the list hasn't been
>>> reviewed.
>>
>> Hmph, I do not particularly see that happening.
>
> Observer bias.  To verify either claim, could you run some stats on
> the ML archives [1] and report the results?

Do we really need that ? Flaming generates lots of useless discussions
that would be difficult to interpret/extract from your numbers.
I think we should focus on improving what is left to improve. That is
of course merely my humble opinion.

  reply	other threads:[~2013-06-21 17:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21  4:56 What's cooking in git.git (Jun 2013, #07; Thu, 20) Junio C Hamano
2013-06-21 11:05 ` Ramkumar Ramachandra
2013-06-21 15:51   ` Junio C Hamano
2013-06-21 16:07     ` Ramkumar Ramachandra
2013-06-21 17:07       ` Junio C Hamano
2013-06-21 17:13         ` Ramkumar Ramachandra
2013-06-21 17:32           ` Antoine Pelisse [this message]
2013-06-21 18:26           ` Junio C Hamano
2013-06-21 18:49             ` Ramkumar Ramachandra
2013-06-21 20:31       ` Junio C Hamano
2013-06-22  6:17         ` Ramkumar Ramachandra
2013-06-23 17:21 ` Thomas Rast

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=CALWbr2xzozGkH23pYCj6XvW3nXF47YCEFGhy+-ivQRrW9FVOPg@mail.gmail.com \
    --to=apelisse@gmail.com \
    --cc=artagnon@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;
as well as URLs for NNTP newsgroup(s).