From: Nigel Cunningham <ncunningham@cyclades.com>
To: Kasper Sandberg <lkml@metanurb.dk>
Cc: Pavel Machek <pavel@suse.cz>,
Thomas Maier <Thomas.Maier@uni-kassel.de>,
linux-kernel@vger.kernel.org
Subject: Re: [Suspend2-announce] Nigel's work and the future of Suspend2.
Date: Fri, 10 Mar 2006 07:34:36 +1000 [thread overview]
Message-ID: <200603100734.42562.ncunningham@cyclades.com> (raw)
In-Reply-To: <1141916144.1745.8.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
Hi.
On Friday 10 March 2006 00:55, Kasper Sandberg wrote:
> > Except that suspend2 is not going to be merged, for variety of
> > reasons. One of them is that noone is working on merging it...
>
> one of them being the operative word, afaik, nigel was unwilling to work
> on the issues needed for merging for the reason that it wouldnt be
> merged..
Yes. The only reason I'm not going to commit myself to getting carried away
with seeking to merge it is that you've clearly stated that you don't want to
see it merged, and you haven't been overruled by other kernel maintainers
(with perhaps the occasional exception, sometimes privately). If they came
along to the party and said "Pavel, get your act together. Suspend2 isn't as
invasive or ugly as you're making it out to be." (or something similar), I'd
see some point to working on merging it. If they want to tell me to submit it
again or prove that's the case, I'm more than willing to hear that. But while
the only feedback is users saying "I wish it was merged" and Pavel saying
"Ain't going to happen", what am I meant to do?
Regards,
Nigel
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-03-09 21:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 0:05 Nigel's work and the future of Suspend2 Nigel Cunningham
2006-03-07 13:14 ` [Suspend2-announce] " Thomas Maier
2006-03-08 12:25 ` Pavel Machek
2006-03-08 17:45 ` Thomas Maier
2006-03-08 20:39 ` Rafael J. Wysocki
2006-03-18 6:08 ` Tom Marshall
2006-03-20 8:13 ` Stefan Seyfried
2006-03-20 13:24 ` Mark Lord
2006-03-08 20:41 ` Pavel Machek
2006-03-09 11:33 ` Kasper Sandberg
2006-03-09 11:45 ` Pavel Machek
2006-03-09 14:55 ` Kasper Sandberg
2006-03-05 0:37 ` Pavel Machek
2006-03-09 21:34 ` Nigel Cunningham [this message]
2006-03-09 22:41 ` Pavel Machek
2006-03-10 4:53 ` Kasper Sandberg
2006-03-07 19:50 ` Bill Davidsen
2006-03-08 18:59 ` Lee Revell
2006-03-08 23:34 ` Nigel Cunningham
2006-03-08 12:21 ` Pavel Machek
2006-03-08 12:27 ` Nigel Cunningham
2006-03-08 21:55 ` Joshua Kugler
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=200603100734.42562.ncunningham@cyclades.com \
--to=ncunningham@cyclades.com \
--cc=Thomas.Maier@uni-kassel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
--cc=pavel@suse.cz \
/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