From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Nigel Cunningham <ncunningham@crca.org.au>
Cc: "linux-pm" <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"TuxOnIce-devel" <tuxonice-devel@lists.tuxonice.net>
Subject: Re: What to do?
Date: Thu, 20 Aug 2009 17:24:34 +0200 [thread overview]
Message-ID: <200908201724.34430.rjw@sisk.pl> (raw)
In-Reply-To: <4A8CCF95.9030401@crca.org.au>
On Thursday 20 August 2009, Nigel Cunningham wrote:
> Hi all.
Hi,
> A few months back, I posted TuxOnIce for something like the third time,
> seeking to see if we could make some progress on getting it merged. The
> outcome of that was an agreement between Rafael and I that we'd work on
> getting TuxOnIce functionality (if not the actual code) merged bit by
> bit, improving swsusp rather than doing an outright merge.
>
> Unfortunately, as the intervening months have shown, Rafael is busy with
> other things and so am I. The few patches I did prepare and post have
> had no review, and I haven't had a chance to build on or rework them
> since. (I'd actually like them not to be merged, because I've realised
> that there are more foundational changes that need to go in first.)
>
> Given that this has been the outcome so far, I see no reason to imagine
> that we're going to make any serious progress any time soon.
That unfortunately is probably right.
The problem for my part is that new things are still appearing that I need to
take care of rather urgently.
In fact the user space part of (u)swsusp also has been suffering from the lack
of attention recently, so to speak.
> I'd therefore like to ask whether there's anyone out there who could do
> one or more of:
>
> 1) Step up to the plate and help improve swsusp, without relying on any
> help from me but with my blessing if they choose to copy wholesale bits
> of TuxOnIce;
> 2) Take over maintaining TuxOnIce from me;
> 3) Some other way forward that hasn't occurred to me.
>
> Thoughts, input, flames, whatever else welcome. A lack of deadly silence
> would be especially appreciated :)
Well, the code is out there. If there's time to try to get it in, I think it's
worth doing.
Best,
Rafael
next prev parent reply other threads:[~2009-08-20 15:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 4:22 What to do? Nigel Cunningham
2009-08-20 15:24 ` Rafael J. Wysocki
2009-08-20 15:24 ` Rafael J. Wysocki [this message]
2009-08-23 19:04 ` [TuxOnIce-devel] " Xavier Gnata
2009-08-24 4:33 ` Nigel Cunningham
2009-08-24 4:33 ` Nigel Cunningham
2009-08-23 19:04 ` Xavier Gnata
2009-08-23 20:13 ` Jiri Slaby
2009-08-23 22:04 ` Rafael J. Wysocki
2009-08-23 22:04 ` Rafael J. Wysocki
2009-08-23 23:07 ` Nigel Cunningham
2009-08-23 23:20 ` Rafael J. Wysocki
2009-08-23 23:20 ` Rafael J. Wysocki
2009-09-07 10:06 ` Jiri Slaby
2009-09-07 10:06 ` Jiri Slaby
2009-08-23 23:07 ` Nigel Cunningham
2009-08-23 20:13 ` Jiri Slaby
-- strict thread matches above, loose matches on Subject: below --
2009-08-20 4:22 Nigel Cunningham
2004-09-03 11:51 Андрiй Яремко
2004-09-03 12:16 ` Clemens Ladisch
2004-09-03 14:11 ` Jaroslav Kysela
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=200908201724.34430.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=ncunningham@crca.org.au \
--cc=tuxonice-devel@lists.tuxonice.net \
/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.