| === henrix_ is now known as henrix | ||
| === Guest79141 is now known as lag | ||
| caribou | Any quick git trick to know when a specific commit made it to the Ubuntu kernel ? | 09:29 |
|---|---|---|
| smb | caribou, Generally (if it does not have to be automated), search for the commit message in git log, then you can use that sha1 in a "git describe --contains" | 09:34 |
| smb | All usually on the master branch | 09:34 |
| caribou | smb: I already had the hash thanks looks like it's what I need | 09:35 |
| smb | caribou, The last step of course is usually to ask rmadison where that version is (-proposed or -updates) | 09:36 |
| === davmor2__ is now known as davmor2 | ||
| === zequence_ is now known as zequence | ||
| arges | apw: discussing bug 1323165 | 15:32 |
| ubot5 | bug 1323165 in linux (Ubuntu Trusty) "[HP ProLiant DL380p Gen8] kernel BUG at /build/buildd/linux-3.13.0/mm/memory.c:3756!" [Undecided,Fix committed] https://launchpad.net/bugs/1323165 | 15:32 |
| arges | looks like the patch is in master-next but the bug status wasn't updated | 15:32 |
| apw | yes that appears to be wrong, it has a bug link so it should just be flipped as you suggest | 15:33 |
| arges | cool | 15:35 |
| rtg | looks like the patch committer was too lazy or stupid to do the right thing. | 15:35 |
| apw | lets assume lazy :) | 15:37 |
| === jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues June 17th, 2014 - 17:00 UTC || If you have a question just ask, and do wait around for an answer! If the question is should I file a bug for something, likely you can assume yes. | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!