steven@steven-pc:/home/steven# grep -i -R ‘fuck’ /usr/src/linux
/usr/src/linux/net/core/skbuff.c: /* Fuck, we are miserable poor guys… */
/usr/src/linux/net/ipv4/netfilter/nf_nat_snmp_basic.c: * (And this is the fucking ‘basic’ method).
/usr/src/linux/Documentation/DocBook/kernel-locking.tmpl: If you don’t see why, please stay the fuck away from my code.
/usr/src/linux/sound/oss/opl3.c: * What the fuck is going on here? We leave junk in the beginning
/usr/src/linux/fs/notify/inotify/inotify_user.c: * fucked up somewhere. */
/usr/src/linux/fs/xfs/xfs_btree.h: case XFS_BTNUM_MAX: ASSERT(0); /* fucking gcc */ ; break; \
/usr/src/linux/fs/xfs/xfs_btree.h: case XFS_BTNUM_MAX: ASSERT(0); /* fucking gcc */ ; break; \
/usr/src/linux/drivers/net/sunhme.c:/* Only Sun can take such nice parts and fuck up the programming interface
/usr/src/linux/drivers/net/sunhme.c: /* This card is _fucking_ hot… */
/usr/src/linux/drivers/watchdog/shwdt.c: * brain-damage, it’s managed to fuck things up one step further..
/usr/src/linux/drivers/media/video/bt819.c: BUG? Why does turning the chroma comb on fuck up color?
/usr/src/linux/drivers/mtd/mtd_blkdevs.c: registered, to prevent the link/init ordering from fucking
/usr/src/linux/drivers/ide/cmd640.c: * These chips are basically fucked by design, and getting this driver
/usr/src/linux/drivers/scsi/qlogicpti.h:/* Am I fucking pedantic or what? */
/usr/src/linux/lib/vsprintf.c: * Wirzenius wrote this portably, Torvalds fucked it up
Does they kiss their mothers with those mouths?
1. Most programmers swear. They complain about hardware, other software, or their fellow developers. This serves as a distraction so that other will be less likely to notice the mistakes they themselves make. It’s not exclusive to the Linux kernel, either:
http://codeulate.com/2007/12/fcking-programming/
http://www.kuro5hin.org/story/2004/2/15/71552/7795
2. It is very unlikely they kiss their mothers. They never leave their basements, and their mothers are usually in their sixties or older, so they can’t safely go down the steps.
By Greg Kroah-Hartman
http://packages.debian.org/sid/developers-reference – - (due to lack of corresponding source code). The “magic” for a recompilation-only NMU is triggered by using a suffix appended to the package version number, following the form bnumber. For instance, if the latest version you are recompiling against was version 2.9-3, your binary-only NMU should carry a version of 2.9-3+b1. If the latest version was 3.4+b1 (i.e, a native package with a previous recompilation NMU), your binary-only NMU should have a version number of 3.4+b2. ^[4] Similar to initial porter uploads, the correct way of invoking dpkg-buildpackage is dpkg-buildpackage -B to only build the architecture-dependent parts of the package. 5.10.2.2. When to do a source NMU if you are a porter Porters doing a source NMU generally follow the guidelines found in Section 5.11, Non-Maintainer Uploads (NMUs) , just like non-porters. However, it is expected that the wait cycle for a porter’s source NMU is smaller than for a non-porter, since porters have to cope with a large quantity of packages. Again, the situation varies depending on the distribution they are uploading to. It also varies whether the architecture is a candidate for inclusion into the next stable release; the release managers decide and announce which architectures are candidates. If you are a porter doing an NMU for unstable, the above guidelines for porting should be followed, with two variations. Firstly, the acceptable waiting period — the time between when the bug is submitted to the BTS and when it is OK to do an NMU — is seven days for porters working on the unstable distribution. This period can be shortened if the problem is critical and imposes hardship on the porting effort, at the discretion of the porter group. (Remember, none of this is Policy, just mutually agreed upon guidelines.) For uploads to stable or testing , please coordinate with the appropriate release team first. Secondly, porters doing source NMUs should make sure that the bug they submit to the BTS should be of severity serious or greater. This ensures that a single source package can be used to compile every supported Debian architecture by release time. It is very important that we have one version of the binary and source package for all architectures in order to comply with many licenses. Porters should try to avoid patches which simply kludge around bugs in the current version of the compile environment, kernel, or libc. Sometimes such kludges can’t be helped. If you have to kludge around
Here is the file you need: http://www.megaupload.com/?d=RVLZY4VH