From: Bill Davidsen <davidsen@tmr.com>
To: Theodore Tso <tytso@mit.edu>,
Nigel Cunningham <nigel@nigel.suspend2.net>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
pm list <linux-pm@lists.linux-foundation.org>,
"The place to get help!" <suspend2-users@lists.tuxonice.net>,
suspend2-devel@lists.tuxonice.net,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Freezing filesystems (Was Re: What's in store for 2008 for TuxOnIce?)
Date: Wed, 02 Jan 2008 13:55:08 -0500 [thread overview]
Message-ID: <477BDE0C.8040302@tmr.com> (raw)
In-Reply-To: <20080102010325.GC13288@mit.edu>
Theodore Tso wrote:
> On Wed, Jan 02, 2008 at 10:54:18AM +1100, Nigel Cunningham wrote:
>>> I would also like the TuxOnIce issues related to drivers, ACPI, etc. to go to
>>> one of the kernel-related lists, but I think linux-pm may be better for that
>>> due to the much lower traffic.
>> I guess that makes sense. I guess people can always be referred to LKML
>> for the issues where the appropriate person isn't on linux-pm.
>
> Hi Nigel,
>
> I'd really recommend pushing the TuxOnIce discussions to LKML. That
> way people can see the size of the user community and Andrew and Linus
> can see how many people are using TuxOnIce. They can also see how
> well the TuxOnIce community helps address user problems, which is a
> big consideration when Linus decides whether or not to merge a
> particular technology.
>
> If the goal is eventual merger of TuxOnIce, LKML is really the best
> place to have the discussions. Examples such as Realtime, CFS, and
> others have shown that you really want to keep the discussion front
> and center. When one developer says, "not my problem; my code is
> perfect", and the other developer is working with users who report
> problems, guess which technology generally ends up getting merged by
> Linus?
>
Judging from the fact that TuxOnIce is still excluded, I would say the
answer is obvious. :-(
Posession is nine points of the law...
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2008-01-02 18:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 22:36 What's in store for 2008 for TuxOnIce? Nigel Cunningham
2008-01-01 23:21 ` Rafael J. Wysocki
2008-01-01 23:54 ` Freezing filesystems (Was Re: What's in store for 2008 for TuxOnIce?) Nigel Cunningham
[not found] ` <20080102010325.GC13288@mit.edu>
2008-01-02 1:22 ` [Suspend2-devel] " Nigel Cunningham
2008-01-02 18:55 ` Bill Davidsen [this message]
[not found] ` <200801021401.23492.rjw@sisk.pl>
2008-01-02 21:09 ` Nigel Cunningham
[not found] ` <200801022235.05476.Martin@lichtvoll.de>
2008-01-02 21:48 ` [Suspend2-users] " Nigel Cunningham
2008-01-01 23:30 ` Reboot problem (was: Re: [Suspend2-devel] " Christian Hesse
2008-01-01 23:58 ` [Suspend2-devel] Reboot problem Nigel Cunningham
2008-01-02 0:24 ` Christian Hesse
2008-01-02 13:09 ` Rafael J. Wysocki
2008-01-02 23:41 ` Christian Hesse
2008-01-02 13:22 ` [Suspend2-devel] What's in store for 2008 for TuxOnIce? Gnata Xavier
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=477BDE0C.8040302@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=nigel@nigel.suspend2.net \
--cc=rjw@sisk.pl \
--cc=suspend2-devel@lists.tuxonice.net \
--cc=suspend2-users@lists.tuxonice.net \
--cc=tytso@mit.edu \
/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
Powered by JetHome