Re: Which is simpler? (Was Re: [Suspend2-devel] Re: [ 00/10] [Suspend2] Modules support.)

[Pavel Machek]

On Po 20-02-06 11:05:34, Sebastian Kügler wrote:
> On Monday 20 February 2006 10:39, Matthias Hensler wrote:
> > > > The only con I see is the complexity of the code, but then again,
> > > > Nigel
> > >
> > > ..but thats a big con.
> >
> > So why is that? From what I see, most of the code is completly independ
> > of the rest of the kernel, and just does not affect if it is disabled.
> >
> > It won't do any harm to the kernel, and again, Nigel is constantly
> > improving that situation, so for sure, that is no _big_ con.
> 
> I might add that you'd drag a devoted developer into the kernel team more 
> closely, which probably makes up for the 'added complexity' anyway.

I'd love to have Nigel helping me and kernel, but he's not
interested. He wants suspend2 merged, he does not want better suspend
in kernel.

> The gain in working *together* on suspend2 is worth much more than the 'added 
> complexity' Pavel complains about. Nigel has stated more than once that he'd 
> be happy to maintain suspend2, and he's done so for quite some time already, 
> which proves his point. Nigel is paid to work on suspend2, so it's not likely 
> to go away once he has a new hobby (and again, he's been doing great work for 
> some time already). 

I do not think he's paid for suspend2 any more.

> So what about working on merging suspend2 finally? Having a proven, stable and 
> feature-rich implemenation available quickly, *and* someone who maintains 
> *and* support it actively does not sound like a bad deal to me.

Nigel is not really maintaining it. He's willing to solve small
problems, but not the big ones.

> One should not underestimate the gains that a suspend2 merge has on the 
> development merely by stating 'added complexity', that pays off _any_day_.
> 
> By the way, does 'working on uswsusp' mean that Pavel and will put less work 
> in maintaining swsusp? That does not sound too promising to my sore ears.

uswsusp and swsusp share most of the important code (go take a
look). No, in-kernel swap writing is not going to be improved too
much, just the bugs fixed. That means very stable swsusp in kernel...

> Personally, to work with, I'd prefer a developer who's responsibly dealing 
> with users' questions and problems any day to one who rejects 99% of emails 
> that don't contain a patch and 95% of those that contain one, stating 'WTF, I 
> don't like that'.

Fine, feel free to help with answering users mails.
									Pavel
-- 
Web maintainer for suspend.sf.net (www.sf.net/projects/suspend) wanted...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/