Hi again. So - trying to get back to the original discussion - what (if anything) do you see as the way ahead? The options I can think of are (starting with things I can do): 1) I stop developing Suspend2, thereby pushing however many current Suspend2 users to move to [u]swsusp and seek to get that up to speed. 2) I quit my day job, see if Redhat will take me full time and give me the time to start trying to merge Suspend2 bit by bit. Alternatively, days suddenly become 8 hours longer and I discover the boundless energy and alertness needed to do this too :). Ok. Not going to happen. 3) Someone else steps up to the plate and tries to merge Suspend2 one bit at a time. 4) uswsusp and swsusp get dropped and Suspend2 goes into mainline. 5) Everything gets dropped and we start from scratch. 6) The status quo - or some small variant of it - stays. Oh... I said "way ahead". I guess that rules this one out, even though I'll be very surprised if it's not the one that wins out. 7) Suspend2 gets merged and people get to choose which they like better. Nearly forgot this as a conceivable possibility. Yeah, I know you said you don't want it. I'm just trying to think of what might possibly happen. N.
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- Re: Back to the future.
- From: Bojan Smojver <[email protected]>
- Re: Back to the future.
- From: Jan Engelhardt <[email protected]>
- Re: Back to the future.
- From: "Pekka Enberg" <[email protected]>
- Re: Back to the future.
- Prev by Date: [PATCH 02/12] NetLabel: convert a BUG_ON in the CIPSO code to a runtime check
- Next by Date: [PATCH 03/12] SELinux: extract the NetLabel SELinux support from the security server
- Previous by thread: [PATCH 0/12] SELinux patches for 2.6.22
- Next by thread: Re: Back to the future.
- Index(es):