Hi!
>> > only "non compressed" part to reach mainline for 2.6. Feature freeze
>> > was few months ago, and "adding possibility to compress swsusp data"
>> > does not sound like a bugfix to me...
>>
>> Feature freeze is always half unfrozen anyway. 2.4 just gained XFS!
>> I'm
>
> XFS probably has 10+ people working on it, full time, and it still
> required quite a lot of pushing.
We could push harder. Should we ask all swsusp2 users using
compression to announce themselves on LKML? ;)
Hmm, I've one such troll announcing into my inbox, sending stuff like
below. I hope he's the only one.
Subject: Microsoft RULES!!!
To: Pavel Machek <pavel@xxxxxx>
...
So stop spreading nonsense about "NO COMPROMISES" and
stop comparing
me to Mickey$oft. Thanks.
---------------------
Such a CUNT!!! Microsoft do very well engineered
software, something Linux can't sadly achive in ages
if still emply LOOSERS LIKE U.
When a Microsoft engineer see a people like u, simply
laugh!!!
U MORON. U ARE SUCH A STUPID CUNT, NOW ALL THE LIST
KNOW ABOUT U, WE ALL LAUGHT!
and
So swsusp2 does _not_ fail. You still have a usablesystem instead of apaniced system you seem to like to accept.
If swsusp1 panics system, that's a bug. I'm not
accepting that one.
Refusing to suspend (I'd call it "fail to suspend") is
bad but is not
a bug. Do we understand each other now?
-------------
U know, I used to call u your name this days: STUPID,
IDIOT, MORON, but that's not enough.
Your last sentence related with your CRAPPY, LURID,
DANGEROUS swsusp1 qualify u as what u are.
A WORST GEEK, A LOOSER, A STUPID CUNT: U WONT EVER
ADMIT YOUR PROGRAM CRASH AND THAT IS A BUG :-((((