From: Rogan Dawes <lists@dawes.za.net>
To: Quim K Holland <qkholland@gmail.com>
Cc: gi mailing list <git@vger.kernel.org>
Subject: Re: Time to flush Mr. Hammano?
Date: Mon, 21 Jan 2008 15:18:53 +0200 [thread overview]
Message-ID: <47949BBD.6060308@dawes.za.net> (raw)
In-Reply-To: <20070624192215@qkholland.gmail.com>
Quim K Holland wrote:
> "Marco Costalba" <mcostalba@gmail.com> wrote:
>
> Reading mailing list threads it is becoming common these days to hear
> about contributors with patches ready to be sent as soon as 1.5.4 is
> out.
>
> Would be a good idea to open a new branch new_stuff as a target for
> this pending stuff?
>
> Back when Mr. Torvalds was still leading the development there was
> not this stupid stability freeze and many useful patches were
> accepted every day. For the past few months Mr. Hammano has not been
> adding much useful code himself, did not join interesting discussions
> such as Unicode normalization issues, nor gave much useful comments
> on patches. He has mostly been busy rejecting useful patches and
> sending not so useful comments.
>
> Can we vote Mr. Hammano out and ask Mr. Torvalds to come back as the
> project leader? I do not mean any disrespect to Mr. Hammano, but
> don't people think he outlived his usefulness as the project leader?
That's Mr Hamano (one 'm'), and personally, I think that only when you
have contributed to this project yourself, would you have a leg to stand
on when you criticise him.
As an observer, I think that Junio is doing a superb job of managing the
sometimes quite torrential flow of patches contributed to git. As Linus
himself has often said (Paraphrased, of course):
The role of the maintainer is often more to *reject* patches than to
accept them, so as to maintain the quality of the code base.
Having said that, the amount of *constructive* criticism that
accompanies those rejections is amazing. Often I have seen multiple
pages of response to a 2 line patch, so that the contributor (and other
observers) can better understand the reason for the rejection, and how
to construct a better patch that would be accepted.
Regards,
Rogan
next prev parent reply other threads:[~2008-01-21 13:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 10:10 Time to flush developer accumulated patches? Marco Costalba
2008-01-20 10:18 ` Wincent Colaiuta
2008-01-20 10:24 ` Marco Costalba
2008-01-20 10:47 ` Steffen Prohaska
2008-01-20 13:49 ` Johannes Schindelin
2008-01-20 20:05 ` Junio C Hamano
2008-01-21 11:15 ` Time to flush Mr. Hammano? Quim K Holland
2008-01-21 11:36 ` David Kastrup
2008-01-21 11:42 ` Junio C Hamano
2008-01-21 11:47 ` Imran M Yousuf
2008-01-21 11:38 ` Paolo Ciarrocchi
2008-01-21 11:39 ` Juanma Barranquero
2008-01-21 12:26 ` Johannes Schindelin
2008-01-21 13:18 ` Rogan Dawes [this message]
2008-01-21 14:12 ` David Tweed
2008-01-21 18:07 ` Marco Costalba
2008-01-21 19:13 ` Jakub Narebski
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=47949BBD.6060308@dawes.za.net \
--to=lists@dawes.za.net \
--cc=git@vger.kernel.org \
--cc=qkholland@gmail.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).