All of lore.kernel.org
 help / color / mirror / Atom feed
From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Split of the normal mode
Date: Sun, 29 Mar 2009 22:38:56 +0200	[thread overview]
Message-ID: <49CFDC60.3060706@gmail.com> (raw)
In-Reply-To: <20090329.132416.79693875.davem@davemloft.net>

I agree. Developers should feel that their work is appreciated. 
Otherwise they turn to something else. THis is especially true for 
opensource where the only holding factor is the motivation

David Miller wrote:
> From: "Yoshinori K. Okuji" <okuji@enbug.org>
> Date: Sun, 29 Mar 2009 21:55:34 +0900
> 
>> On Sunday 29 March 2009 20:40:17 David Miller wrote:
>>> From: "Yoshinori K. Okuji" <okuji@enbug.org>
>>> Date: Sun, 29 Mar 2009 20:29:26 +0900
>>>
>>>> So if nobody else can, I would like to get it straight again myself,
>>>> although I am pretty busy (as I have a startup company, can you
>>>> imagine how tough it is?).
>>> Everybody is too busy to give this project the attention and time it
>>> deserves to be maintained properly.
>>>
>>> I honestly do not think the situation will change significantly until
>>> someone is able to devote real time as a maintainer and process all of
>>> the patches that get submitted each day.
>> This is ideal but not absolutely required. If you look at some popular 
>> projects, such as Linux and Firefox, you can find out that not all (actually, 
>> very few) patches are handled so quickly, but those projects are functioning 
>> so well.
> 
> As a top-level maintainer in one of those projects, I beg to differ.
> 
> The only reason I have so many people underneath me actively working
> on the Linux networking stack is the simple fact that I process all
> new patches processed each and every day.  I sometimes apply 100 or
> more patches in a day, and that's critical for keeping the project
> healthy.
> 
> And I do it using email because that is what's easiest for developers.
> It is so easy to track patches automatically, using email instead of
> some bug system, using a facility such as patchwork.
> 
> Otherwise I'd have the situation you guys have here, frustrated
> developers and slow progress.
> 
> You can keep denying that this matters, but my practical experience
> of over 15 years disagrees with your's.
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel


-- 

Regards
Vladimir 'phcoder' Serbinenko



  reply	other threads:[~2009-03-29 20:39 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-29  9:25 [PATCH] Split of the normal mode Bean
2009-03-29  9:40 ` Vesa Jääskeläinen
2009-03-29 10:09   ` Yoshinori K. Okuji
2009-03-29 10:43     ` phcoder
2009-03-29 10:53       ` Vesa Jääskeläinen
2009-03-29 11:33         ` phcoder
2009-03-29 11:51           ` Yoshinori K. Okuji
2009-03-29 12:09             ` Bean
2009-03-29 13:10               ` Yoshinori K. Okuji
2009-03-29 13:59                 ` Bean
2009-03-29 14:20                   ` Yoshinori K. Okuji
2009-03-29 14:30                     ` Bean
2009-03-29 14:54                       ` Yoshinori K. Okuji
2009-03-29 15:17                         ` Bean
2009-03-30 15:42                           ` Yoshinori K. Okuji
2009-03-30 20:04                 ` Colin D Bennett
2009-03-31  6:11                   ` Bean
2009-03-31 15:02                     ` Colin D Bennett
2009-03-29 13:00             ` phcoder
2009-03-29 14:51               ` Yoshinori K. Okuji
2009-03-29 17:07                 ` phcoder
2009-03-29 20:35                   ` phcoder
2009-03-30 15:49                     ` Yoshinori K. Okuji
2009-03-30 15:59                       ` phcoder
2009-04-01  7:43                         ` phcoder
2009-04-01  8:07                           ` David Miller
2009-04-01  9:22                             ` phcoder
2009-04-01 14:10                               ` Yoshinori K. Okuji
2009-04-01 16:14                                 ` phcoder
2009-03-29 11:29       ` Yoshinori K. Okuji
2009-03-29 11:40         ` David Miller
2009-03-29 12:55           ` Yoshinori K. Okuji
2009-03-29 13:23             ` Vesa Jääskeläinen
2009-03-29 14:49               ` Yoshinori K. Okuji
2009-03-29 15:43                 ` Vesa Jääskeläinen
2009-03-29 20:26               ` David Miller
2009-03-29 20:24             ` David Miller
2009-03-29 20:38               ` phcoder [this message]
2009-03-30 15:43                 ` Bean
2009-03-30 16:22                   ` Yoshinori K. Okuji
2009-03-30 16:38                     ` Bean
2009-03-30 16:35                   ` Vesa Jääskeläinen
2009-03-29 11:59         ` General design (was Re: [PATCH] Split of the normal mode) phcoder
2009-03-29 10:48     ` [PATCH] Split of the normal mode Vesa Jääskeläinen
2009-03-29 11:39       ` Yoshinori K. Okuji
2009-03-29 12:17       ` Vesa Jääskeläinen
2009-04-01 13:19     ` Robert Millan
2009-04-01 14:15       ` Yoshinori K. Okuji

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=49CFDC60.3060706@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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.