Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-kernel
Navigation:
Lists: gentoo-kernel: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: Gentoo Kernel List <gentoo-kernel@g.o>
From: mpagano@g.o (Michael Pagano )
Subject: [ANNOUNCE] genpatches-3.0-19 release
Date: Tue, 7 Feb 2012 14:14:03 +0000 (UTC)
This is an automated email announcing the release of genpatches-3.0-19


CHANGES SINCE 3.0-18
-----------------------

Revision 2081: 
Linux patches 3.0.18, 3.0.19 and 3.0.20. Removal of redundant patch (mpagano)
Deleted: 2100_proc-mem-handling-fix.patch

Revision 2084: 
Add Linux patches 3.0.18, 3.0.19 and 3.0.20 (mpagano)
Added: 1017_linux-3.0.18.patch
Added: 1018_linux-3.0.19.patch
Added: 1019_linux-3.0.20.patch

Revision 2085: 
3.0-19 release (mpagano)


PATCHES
-------

When the website updates, the complete patch list and split-out patches will be
available here:
http://dev.gentoo.org/~mpagano/genpatches/patches-3.0-19.htm
http://dev.gentoo.org/~mpagano/genpatches/tarballs/genpatches-3.0-19.base.tar.bz2
http://dev.gentoo.org/~mpagano/genpatches/tarballs/genpatches-3.0-19.extras.tar.bz2


ABOUT GENPATCHES
----------------

genpatches is the patchset applied to some kernels available in Portage.

For more information, see the genpatches homepage:
http://dev.gentoo.org/~mpagano/genpatches

For a simple example of how to use genpatches in your kernel ebuild, look at a
recent gentoo-sources ebuild.


Navigation:
Lists: gentoo-kernel: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
[ANNOUNCE] genpatches-3.2-8 release
Next by thread:
[ANNOUNCE] genpatches-3.2-9 release
Previous by date:
[ANNOUNCE] genpatches-3.2-8 release
Next by date:
[ANNOUNCE] genpatches-3.2-9 release


Updated Jun 23, 2012

Summary: Archive of the gentoo-kernel mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.