[03:19] <bazhang> wondering if Ubuntu-mobile will work on the eeepc (eeeuser.com)
[03:30] <bazhang> I see the Kojinsha sh6 (sp?) but not the eeepc; any chance that will added later--similar intel chipset I believe.
[03:30] <bazhang> oops in the wiki
[03:35] <nrp> sh6 and the others are A100/A110, arent they?
[03:35] <nrp> eee is a celeron
[03:36] <bazhang> you're right. is that a problem?
[03:36] <bazhang> too powerful?
[03:37] <nrp> no idea, theyre both x86.  not sure if they use the same/similar northbridges though
[03:38] <nrp> does the a110 even have a northbridge? or is it all integrated into the cpu?
[03:38] <bazhang> got me there--though the wiki does state this will possibly work on other i386 
[03:39] <nrp> ah, has anyone tried it?
[03:40] <bazhang> I'll do it, as soon as they have some packages--currently waiting for a Debian live installer in the next couple of days.
[13:29] <HappyCamp_2> StevenK: a favor? :)
[13:29] <HappyCamp_2> The pyinotify package:  https://launchpad.net/ubuntu/+source/pyinotify/0.7.0-2ubuntu1/+build/364671
[13:29] <StevenK> HappyCamp_2: Name?
[13:29] <StevenK> Um
[13:29] <StevenK> HappyCamp_2: Name it?
[13:29] <HappyCamp_2> I'm waving at you
[13:30] <HappyCamp_2> We need a slight modification to the package to make it lpia.
[13:33] <bspencer> HappyCamp_2: python-inotify and gstreamer0.10-plugins-bad-multiverse  ?
[13:33] <HappyCamp_2> bspencer: yep
[13:33] <bspencer> I just read cathy's email.  
[13:33] <bspencer> you're doing that?
[13:38] <HappyCamp_2> StevenK: what does "bad-multiverse" mean in "gstreamer0.10-plugins-bad-multiverse"
[13:38] <HappyCamp_2> Is it a screwed up package?
[13:39] <StevenK> HappyCamp_2: Nope.
[13:40] <HappyCamp_2> bad license?
[13:40] <StevenK> HappyCamp_2: Firstly, -multiverse points to the fact that due to licensing, it's in multiverse.
[13:40] <HappyCamp_2> that I think I got, the bad was the confusing part
[13:41] <StevenK> HappyCamp_2: Secondly, -bad is from upstream. Gstreamer upstream declares codecs they support as good, bad, and ugly. Good is it's well supported, Bad is it's okay-ish supported, and Ugly is if it breaks, you get all of the pieces
[13:42] <HappyCamp_2> Ah, okay.  I was maybe thinking "bad" was some debian/ubuntu declaration.  Thanks for clarifying StevenK 
[13:42] <StevenK> HappyCamp_2: No problem
[13:50] <HappyCamp_2> Sciri: what do you get if you run the command: sudo smartctl -d ata -a /dev/sda | grep 193
[13:51] <HappyCamp_2> I was reading this, that was slashdotted.  https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695
[13:51] <ubotu> Launchpad bug 59695 in acpi-support "default value in power.sh potentially kills laptop disks (dup-of: 17216)" [Wishlist,Confirmed] 
[13:51] <ubotu> Launchpad bug 17216 in acpi-support "Hard drive spindown should be configurable" [High,Fix committed] 
[13:53] <Sciri> HappyCamp_2: I'm on VMWare on the Mac. ;) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
[13:53] <Sciri> HappyCamp_2: I do however have my SMART stats on the Mac side...
[13:53] <HappyCamp_2> Sciri: then I doubt it would apply to you then.
[13:54] <Sciri> HappyCamp_2: Yeah, elmo had me check the Mac side of things last night to compare Mac stats to Ubuntu stats.
[14:03] <lool> StevenK: It's the other way around: -bad are the really bad plugins which either are broken or have major issues to promote them; ugly is for plugins which have distribution issues but are otherwise fully ok (work fine, has documentation, etc.) such as being GPL
[14:03] <StevenK> Ah ha
[14:03] <bspencer> smagoun:  can you give me the URL for your email mockup again?
[14:03] <smagoun> bspencer: https://wiki.ubuntu.com/MobileAndEmbedded  . Scroll down to the "Example UIs section"
[14:04] <bspencer> thx
[14:08] <HappyCamp_2> instability = pain
[14:08] <HappyCamp_2> bspencer: 
[14:09] <bspencer> HappyCamp_2: 
[14:10] <lool> bspencer: 
[14:11] <HappyCamp_2> lool: I have a patch for x264 can you check it out?
[14:12] <lool> HappyCamp_2: Sure
[14:12] <lool> I don't know whether I can upload to multiverse, but I guess so?
[14:12] <lool> HappyCamp_2: If it's an upstream fix, I can push it upstream actually and down to Ubuntu via Debian
[14:12] <HappyCamp_2> http://moblin.pastebin.org/6605
[14:12] <HappyCamp_2> lool
[14:13] <HappyCamp_2> Okay, I'm not sure which one it is.
[14:13] <HappyCamp_2> It is in the x264 package.
[14:13] <lool> Ok
[14:13] <HappyCamp_2> I don't think it is a major change, but the package failed to build in lpia.
[14:14] <lool> I'm fixed it in the Debian SVN (well it's an unofficial repo)
[14:15] <HappyCamp_2> lool thanks :)  So how long would that take to propogate to Ubuntu?
[14:15] <lool> It wont propagate to Ubuntu via Debian like I thought first as it's not in Debian officially; I'll prepare an upload to Ubuntu now
[14:16] <HappyCamp_2> lool, excellent!
[14:26] <HappyCamp_2> bspencer: do you have an email that you are checking from your Ubuntu system?
[14:29] <HappyCamp_2> bspencer: s/email/email address/
[14:30] <bspencer> I'm currently in Windows going through my mail. 
[14:30] <bspencer> After I boot back into Ubuntu I don't have mail acces
[14:30] <bspencer> s
[14:31] <HappyCamp_2> bspencer: I was thinking maybe you had a gmail or something account that you could use
[14:31] <HappyCamp_2> anyway I sent email to you intel.com account just now.
[14:31] <bspencer> yeah.  I do if you want to send it to chefebe at gmail
[14:31] <bspencer> though you'll have to tell me to check it because it is just a spam account now
[14:31] <HappyCamp_2> check you intel email :)
[14:39] <lool> HappyCamp_2: It's in
[14:39] <HappyCamp_2> lool, thanks so is that allowed to go into Gutsy? 
[14:40] <HappyCamp_2> Since it didn't even build at all in Gutsy.
[14:40] <lool> HappyCamp_2: No, I uploaded to hardy; technically that's perhaps important enough a bug to be allowed in a SRU, but "multiverse" makes it much less likely to be and a SRU is a lot of work
[14:41] <HappyCamp_2> :(  bspencer see what lool said?
[14:41] <HappyCamp_2> https://launchpad.net/ubuntu/+source/x264
[14:47] <smagoun> bspencer: I moved a couple documents about mobile UIs to the ubuntu wiki:
[14:47] <smagoun> https://help.ubuntu.com/community/UMEGuide/DesigningForFingerUIs
[14:47] <smagoun> https://help.ubuntu.com/community/UMEGuide/ImprovingUserExperience
[14:47] <smagoun> They're linked from https://help.ubuntu.com/community/UMEGuide
[16:39] <bspencer> Mithrandir: lool   I want to create a new blueprint for mobile
[16:39] <bspencer> I go here: https://blueprints.launchpad.net/ubuntu/
[16:39] <bspencer> and click "add blueprint" button.  How do I associate it with mobile though?
[16:40] <Mithrandir> subscribe ubuntu-mobile to it
[16:40] <bspencer> ah, thx
[16:41] <bspencer> Mithrandir: participatieon essential ?
[16:41] <Mithrandir> no
[16:41] <Mithrandir> that's going to make the scheduler explode
[20:07] <amitk> HappyCamp_2: ping
[20:12] <HappyCamp_2> amitk: here
[20:12] <HappyCamp_2> rob_moblin: thinking about having the meeting here.
[20:13] <robr> HappyCamp_2: OK
[20:15] <HappyCamp_2> amitk: ??
[20:16] <amitk> robr_ubuntu: hello
[20:16] <HappyCamp_2> Okay we got robr and amitk
[20:16] <HappyCamp_2> I think tonyespy was interested too
[20:16] <tonyespy> i'm here
[20:17] <robr> so what's the issue
[20:17] <amitk> so the discussion was about getting moblin patches into Ubuntu
[20:18] <amitk> currently, the patches are dpatches and commits do more than one thing
[20:18] <robr> amitk: you should have the latest patches now for the ones i know about except the following:
[20:18] <amitk> robr_ubuntu: I don't have the latest patches from anyone
[20:18] <amitk> I just know they are in the moblin tree
[20:19] <robr> psb gfx, pierre's sdio stack, and a fix up for the hd audio on C0
[20:19] <robr> amitk: why do you say that?
[20:20] <amitk> robr_ubuntu: 1. They are in dpatch format.
[20:20] <tonyespy> could i jump in for a second and try to explain?
[20:20] <amitk> sure
[20:21] <tonyespy> there are a couple of issues, but the main one that i see is that patches are not being pushed and/or pulled on a regular basis from moblin to ubuntu
[20:22] <tonyespy> thus, the mobile biz unit has had to build custom kernels
[20:22] <robr> tonyespy: when we have patches for you to take we always push them
[20:22] <tonyespy> with individual patches pulled from moblin
[20:22] <robr> tonyespy: which patches?
[20:22] <tonyespy> sdio, marvel8688, alsa...
[20:23] <tonyespy> some of them were pushed, but when the patches were updated, they weren't necessarily pushed again
[20:23] <robr> tonyespy: we will not push marvell's drivers, you need to get them from marvell
[20:23] <robr> the sdio stack is still under development, when it's stable we will push it
[20:24] <tonyespy> we've still needed to grab fixes to the sdio stack for our 'customer'
[20:24] <robr> we've purposed not pushed the sdio stack because it's still under thrash from development
[20:25] <tonyespy> for instance there was an update to the sdio patch that allowed the sd memory cards and the marvell wifi to work at the same time
[20:26] <tonyespy> amit and/or happycamp_2 is mike frey around???  he should be involved in this conv, and perhaps bob as well...
[20:26] <robr> tonyespy: i think that's a special case, that was on the mss stack which we're trying NOT to develop on any long and trying to work on getting Pierre's new sdio stack production ready
[20:27] <HappyCamp_2> Mike is not here.
[20:27] <amitk> tonyespy might know. I am not in the same room
[20:27] <tonyespy> neither am i.  ;)
[20:27] <robr> tonyespy: we won't push drivers until we consider them stable enough to be pushed, mss is what we're trying to get away from
[20:28] <HappyCamp_2> To me it sounds like the main problem is that there is a lack of communication on what is going on between intel, amit, and canonical lexington.
[20:28] <tonyespy> understood, however we're stuck in the middle trying to manage customer expectations...
[20:28] <tonyespy> yup
[20:29] <HappyCamp_2> Should we add a kernel sync up portion to the weekly ubuntu-mobile meeting that Mithrandir and davidm run?
[20:29] <HappyCamp_2> Just to make sure that people know what is going on?
[20:29] <HappyCamp_2> Thoughts?
[20:29] <tonyespy> that might be useful...
[20:29] <robr> tonyespy: i think it's perfectly reasonable to have you guys pull from our tree while we're doing development -- with better communication
[20:29] <amitk> perhaps we should have a temp tree that can contain these patches so that the lexington team can support customers
[20:29] <davidm> HappyCamp_2, we could but I'm planning on canceling the meeting this week.
[20:29] <robr> amitk: you do, it's called moblin.org ;-)
[20:30] <tonyespy> ;)
[20:30] <HappyCamp_2> davidm: I'm suggesting for future meetings.  
[20:30] <amitk> robr_ubuntu: that is the problem. Because you use the dpatch mechanim, we can't directly pull from your tree... it requires manual massaging
[20:30] <HappyCamp_2> robr but he doesn't like the dpatches.
[20:30] <robr> the meeting agenda item is a good idea, but the meeting time is bad for me -- it would be better if it was at 10am
[20:30] <HappyCamp_2> amitk: what would you like instead of that?
[20:30] <amitk> plain patches 
[20:30] <HappyCamp_2> Maybe we can do something different, though ultimately up to robr
[20:31] <HappyCamp_2> robr thoughts?
[20:31] <amitk> ideally, I would like to be able to just do a git pull from the moblin tree. Currently that's just not possible.
[20:32] <robr> i'm trying to understand why the dpatches are an issue, if you just strip off the header you've got a plain patch-- seems like there's more to it than that
[20:33] <tonyespy> i *think* the issue is that the ubuntu kernel git tree has patches directly applied, whereas moblin stores patches as individual dpatches, therefore it's harder to diff and/or pull between the two trees
[20:33] <tonyespy> is that right amit?
[20:33] <amitk> robr_ubuntu: it means exporting the patches manually, stripping off the header, applying to our tree for every relevant commit
[20:34] <amitk> and then if you do an update, it is rinse, wash, repeat
[20:34] <amitk> it would be nice to be able to just say git cherry-pick <sha> from your tree instead
[20:34] <robr> amitk / tonyespy : we're not going to move to a system where we commit our patches directly to the kernel -- we'll always have patch files
[20:34] <HappyCamp_2> robr why is that?
[20:35]  * HappyCamp_2 is clueless on kernel development
[20:36] <robr> HappyCamp_2: because it's bad form -- i want the pristine source to remain pristine and to be able to keep track of what patches have been applied to the pristine sources
[20:36] <HappyCamp_2> robr but doesn't git allow you to do that?
[20:37] <robr> HappyCamp_2: not when you have tons of commits on top of commits
[20:37] <HappyCamp_2> amitk: any thoughts on that?
 what can I say? Can you atleast notify us of 'beta' patch updates to the aforementioned subsystems? I don't want to be polling the moblin kernel for changes.
[20:39] <tonyespy> along  the same lines as amit...from my Pov, one of the other things that's difficult is knowing when a patch has been updated in the moblin tree; especially when the name of the patch doesn't change...
[20:40] <suihkulokki> As a complete outsider, I'd also be interested in finding out how to use git to maintain a patchset the same way one can with quilt (or dpatch, but dpatch sucks:P)
[20:40] <amitk> robr_ubuntu: FWIW, that IS the job of a revision control system.... to track history
[20:40] <robr> amitk: what we can do better is give you patches that work with your kernel tree, which we've been doing in the past. both alek and jacob have given you guys patches that are specific to your tree
[20:40] <tonyespy> robr: yes, a revision system tells you history, but only if you ask
[20:41] <tonyespy> typically an SCS is setup with email notifications...
[20:41] <HappyCamp_2> amitk: I know that I am not a git expert and I am not sure if robr is either.  Maybe we don't know about features in git that would enable us to satisfy robr's desire of being able to have the pristine and all the patches.
[20:41] <HappyCamp_2> But also enable you to cherry-pick the patches.
[20:41] <amitk> robr_ubuntu: yes.. that would make it easy. I haven't received patches from them in a long time though. Not after the original enablement patches.
[20:42] <amitk> HappyCamp_2: no you can't do that.
[20:42] <robr> amitk: that's because we've not really had anything we consider ready to give to you
[20:42] <HappyCamp_2> robr, so I guess they want to know what we are doing even if we don't think it is ready for them.
[20:42] <tonyespy> yes
[20:42] <robr> right, we need better communication
[20:43] <HappyCamp_2> So we should try to have a status notification and let them make the decision if they want the stuff or not.
[20:43] <robr> so let's start with an update now, right here
[20:43] <tonyespy> sure
[20:43] <amitk> robr_ubuntu: Then I guess, the only disagreement is what you think is READY. Since the guys in Lexington could use even beta-class improvements,  we would appreciate knowing about updates to the thermal, SDIO, SD8686,  patches
[20:43] <amitk> tonyespy: did I miss anything?
[20:44] <robr> HappyCamp_2: can they subscribe to the check-in email list -- that would give them notification of changes immediatly
[20:44] <tonyespy> i think we're on top of SD8686, it's a whole other saga...
[20:44] <tonyespy> cool
[20:44] <HappyCamp_2> amitk: So I think we will try to update you on changes, at least once a week, on what we are doing, in whatever form the patches are.  Is that agreeable robr?
[20:45] <HappyCamp_2> robr, yes they can.  http://www.moblin.org/mailman/listinfo/
[20:45] <robr> MSS is dead, we're trying to switch to Pierre's stack -- Feng has been at Marvell this week working with them to integrate their driver on Pierre's stack -- their sd8688 driver is still not gpl'd
[20:45] <HappyCamp_2> https://www.moblin.org/mailman/listinfo/commits
[20:45] <HappyCamp_2> But that is ALL commits at moblin.org.
[20:45] <robr> also you guys can always ask me on irc if you have questions
[20:46] <HappyCamp_2> personally I think a little kernel update during davidm meeting or in the status report sent weekly to ubuntu-mobile would be good too.
[20:46] <robr> what we have on moblin.org now is a patch for mss, pierre's sdio and sd8686
[20:46] <amitk> HappyCamp_2: robr_ubuntu: Thanks. I guess tonyespy will then keep track of changes and inform me of anything that can be pushed into Ubuntu.
[20:47] <robr> HappyCamp_2 : understood
[20:47] <HappyCamp_2> tonyespy: can you pass this info on to mfrey?
[20:47] <HappyCamp_2> #startmeeting
[20:47] <MootBot> Meeting started at 20:47. The chair is HappyCamp_2.
[20:47] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[20:47] <tonyespy> yes, i can pass on to mike
[20:47] <HappyCamp_2> topic kernel communication
[20:48] <HappyCamp_2> [topic] kernel communication
[20:48] <MootBot> New Topic:  kernel communication 
[20:48] <HappyCamp_2> [action] tonyespy to communicate meeting info to mfrey
[20:48] <MootBot> ACTION received:  tonyespy to communicate meeting info to mfrey 
[20:48] <tonyespy> guess i'll also volunteer to grab the commit messages and see if i can create a rule to filter out everything but kernel patches
[20:48] <robr> the other status item is the latest kernel pieces for the Gfx driver, which we're ready to give you now but there will be more changes in about 4 weeks
[20:49] <HappyCamp_2> [action] robr to update Cannoical Lexington and amitk with weekly info on the moblin.org kernel patches
[20:49] <MootBot> ACTION received:  robr to update Cannoical Lexington and amitk with weekly info on the moblin.org kernel patches 
[20:50] <HappyCamp_2> [topic] latest kernel pieces for the Gfx driver
[20:50] <MootBot> New Topic:  latest kernel pieces for the Gfx driver 
[20:50] <tonyespy> robr: are the changes for the Gfx driver commited as a patch in the moblin kernel tree?
[20:51] <robr> i don't have any information on the thermals other than i should be receiving new patches soon, the team in umg working on the thermals is supposed to be working directly with you guys on it -- we were taken out of the loop on that one
[20:52] <robr> tonyespy: no, they're an out-tree driver package
[20:52] <amitk> robr_ubuntu: I only know that there should be some patches for thermal  in 1st week of Nov
[20:52] <tonyespy> ok
[20:53] <HappyCamp_2> amitk: tonyespy Is there anything else that you feel we need to cover.  Anything that robr and I can do?
[20:53] <amitk> I am ok with this arrangement for now. Thanks guys.
[20:54] <tonyespy> robr: can you send me the details on the Gfx driver pieces?  other than that, i *think* we're covered for now.  i'll discuss with mike & amit tomorrow
[20:54] <HappyCamp_2> Okay.  Thanks a lot for your time :)
[20:54] <HappyCamp_2> Thanks for attending robr!
[20:54] <tonyespy> thanks rob!
[20:54] <HappyCamp_2> [action] robr to send details on Gfs driver to tonyespy 
[20:54] <MootBot> ACTION received:  robr to send details on Gfs driver to tonyespy  
[20:54] <HappyCamp_2> #endmeeting
[20:54] <MootBot> Meeting finished at 20:54.
[20:55] <robr> tonyespy: i'll have jacob_p send you the info
[20:55] <tonyespy> ok, thanka again
[20:56] <HappyCamp_2> Log for meeting at: http://kryten.incognitus.net/mootbot/meetings/
[20:58] <jacob_p> tonyespy, the graphics driver kernel piece is in a separate package called psb-kmd
[21:05] <HappyCamp_2> jacob_p: link please
[21:07] <robr> tonyespy HappyCamp_2: http://www.moblin.org/repos/projects/psb-kmd.git/
[21:09] <robr> tonyespy HappyCamp_2 : the corresponding X Windows pieces are here http://www.moblin.org/repos/projects/xf86-video-psb.git/
[21:12] <robr> jacob_p: can you fill in tonyespy with the details of the Beta1 Gfx driver
[21:13] <robr> tonyespy: i'm not sure either jacob_p or i have your email address
[21:15] <tonyespy> rob, sorry had to step away from my desk. my email is: tony.espy@canonical.com
[21:31] <jacob_p> tonyespy, i will send you an email.
[21:32] <awe> thanks jacob
[21:44] <HappyCamp_2> tonyespy: so did you have a name for that club?
[21:47] <Sciri> HappyCamp_2: You going clubbing tonight? ;)
[21:47] <HappyCamp_2> Maybe :)  He said there was a good band playing.
[21:48] <HappyCamp_2> thanks tonyespy 
[21:48] <Sciri> HappyCamp_2: There's Middle East right around the corner. http://www.mideastclub.com/ Rockstar Games Presents : The Big Big Bucks as The Breeders, Indefinite Article as Talking Heads, Baker as The Cars, The Self Righteous Brothers as The Beatles, The Creedence Clearwater Revivalists (Live demos of Manhunt 2 for the Wii and PS2)
[21:48] <Sciri> Don't know if he was talking about one of those. If not there's Avalon and Lansdown Street Clubs.
[21:50] <HappyCamp_2> Sciri: thanks
[21:50] <HappyCamp_2> tonyespy: sorry not using registered nick
[21:51] <Sciri> tonyespy: /msg nickserv register CHOOSE-A-PASSWORD-FOR-IRC
[21:51] <HappyCamp_2> not tonyespy I'm not using a registered nick Sciri 
[21:51]  * HappyCamp_2 is a loser
[21:52] <Sciri> HappyCamp_2: Slacker.
[21:52]  * HappyCamp_2 is a looser, seems like ever more of a loser to misspell it :)
[22:03] <tonyespy> so happy_camp2, not registered nick, so you didn't see any of that stuff i just typed to you???  ;)
[22:07] <tonyespy> oh well... no happy_camp2.   for those interested, there's a great band (   http://www.myspace.com/andreagillis  ) playing at "toast" in union square ( http://www.toastlounge.com/directions/ ).  Music probably starts around 9:30 / 10ish...
[22:08] <tonyespy> forgot to prefix with: "for those at UDS-Boston"...
[22:08] <tonyespy> follow the directions from "Back Bay"...
[22:09] <amitk> robr_ubuntu: ping
[22:10] <amitk> robr_ubuntu, jacob_p: Are the changes to psb _required_ for C0?
[22:15] <robr> amitk: no
[22:16] <robr> amitk: as far as i know that is, as we've got no C0 hardware to test on
[22:17] <amitk> we tried booting an lpia kernel on the C0. Kernel boots fine, but modprobe psb gives a garbled screen
[22:19] <amitk> robr_ubuntu: ^^^
[22:19] <robr> amitk: that's strange -- are you guys using the latest and greatest image-creator ?
[22:20] <robr> that is, the one on moblin.org as opposed to the deb package in gutsy
[22:21] <robr> moblin-image-creator on moblin.org will break on your kernel because the fsets are trying to pull in the new psb X driver which requires the new psb.ko driver
[22:22] <amitk> this was using the gutsy M-I-c
[22:23] <robr> amitk: do you know when that was pulled from moblin.org? 
[22:24] <amitk> robr_ubuntu: Just wanted to confirm that there is no psb<-->C0 dependency.
[22:24] <rob_moblin> as far as we know, no
[22:24] <amitk> robr_ubuntu: no idea. but it has to be atleast 3 weeks old
[22:25] <rob_moblin> then you should be safe from the issue i was talking about
[22:25] <rob_moblin> we've never tried the old psb driver on C0 hw as we don't have C0 hw
[22:27] <HappyCamp_2> rob_moblin: I am trying to build an image for the CB, what FSETs should I install
[22:28] <HappyCamp_2> rob_moblin: ??
[22:30] <rob_moblin> HappyCamp_2: moblin-crownbeach-full-mobile-stack-with-proprietary plus ubuntu-staging
[22:30] <HappyCamp_2> rob_moblin: what order?
[22:30] <HappyCamp_2> does it matter?
[22:31] <rob_moblin> HappyCamp, in that order
[22:31] <HappyCamp_2> k
[22:31] <rob_moblin> ubuntu-staging should be last
[22:34] <lucasr> hi all
[22:51] <HappyCamp_2> rob_moblin: it booted :)
[22:52] <rob_moblin> HappyCamp_2, fantastic
[23:09] <lucasr> vuntz, ping