grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Split of the normal mode


From: David Miller
Subject: Re: [PATCH] Split of the normal mode
Date: Sun, 29 Mar 2009 13:24:16 -0700 (PDT)

From: "Yoshinori K. Okuji" <address@hidden>
Date: Sun, 29 Mar 2009 21:55:34 +0900

> On Sunday 29 March 2009 20:40:17 David Miller wrote:
> > From: "Yoshinori K. Okuji" <address@hidden>
> > 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.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]