[00:24] <manjo> jjohansen, around ? 
[00:24] <manjo> :)
[00:48] <jjohansen> manjo: in and out
[00:48] <jjohansen> now
[00:48] <manjo> jjohansen, ah you are not mumbling :) 
[00:49] <manjo> jjohansen, git send-email messed up when I sent to lkml, it did not past the patch but only my text, I had to resend it although I tested it 4 times on my self :(
[00:51] <jjohansen> hrmm strange if it worked on yourself it should have worked on lkml
[00:52] <jjohansen> I have had occasional odd mail failures in the past
[00:52] <jjohansen> ah pulse has muted my audio again
[00:55] <manjo> heh
[00:56] <manjo> it is strange that it worked 4 times for me, and my 1st git email to lkml was blank
[00:56] <jjohansen> did you hit n when it was asking to send an email?
[00:57] <manjo> no I said why
[00:57] <jjohansen> ?
[00:57] <jjohansen> ah silly mumble, I may have to reboot to get audio back
[06:59] <ohsix> is there a proper place to mark internal things on usb as nonremovable? (not kernel related, but i suspect the people here would know)
[07:00] <ohsix> i'm looking at ID_DRIVE_DETACHABLE in udisks/udev rules, but i'm wondering if there isn't some place to mark things internal
[17:03] <pcjc2> If you'll permit me a N00b question, is there any docs anywhere on Ubuntu kernel git policy?
[17:03] <pcjc2> I've been following kernel development from the git repositories, and notice the master branch is often force-updated, which makes the history quite hard to follow. Is there any documented procedures / patch series tools being used, which would help me understand what is going on?
[18:20] <pcjc2> ls
[18:38] <bjf> pcjc2, i'm assuming you are talking about the natty repository?
[18:39] <pcjc2> yes
[18:40] <bjf> pcjc2, the reson it gets force-updated is because we are taking changes from linus's -rc releases right now and until natty freezes, it's our normal policy to rebase onto linus's tree and then force push our master branch
[18:40] <pcjc2> ok, so it is just a rebase
[18:41] <bjf> pcjc2, yes, it's a rebase and then a force push
[18:41] <pcjc2> Btw.. not sure if it is in yet, but there are some important patches which cropped up on the ACPI list recently which fixed suspend issues regarding fans sticking on
[18:41] <bjf> pcjc2, once we freeze/ship we don't do that any more
[18:42] <bjf> pcjc2, linus's tree and lkml are monitored closely, if it comes out in an -rc release we'll get it soon after
[18:42] <bjf> pcjc2, we sometimes grab patches before a -rc if it's significant enough
[18:43] <pcjc2> http://www.kerneltrap.org/mailarchive/linux-kernel/2010/11/24/4650803/thread
[18:44] <bjf> pcjc2, since we had our alpha1 release this week we may not have the latest -rc applied yet
[18:54] <pcjc2> ok, how is that all going?
[18:54] <pcjc2> I'm building natty kernel on maverick so I can more easily backport drm-intel-next
[18:54] <pcjc2> that is working pretty well for me
[18:55] <pcjc2> haven't dared install Natty on this yet (it is my day to day machine), even though I do tend to track from early betas onwards
[20:14] <hrw> hi
[20:15] <hrw> does someone know how to remap keyboard on text console and x11?
[20:59] <osmosis> is it possible to create a file from a  /proc/####/fd/#  reference?