| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Package-Manager: portage-2.2.1/cvs/Linux x86_64
RepoMan-Options: --ignore-arches
Manifest-Sign-Key: 0xA792A613
|
|
|
|
|
| |
Package-Manager: portage-2.1.12.2/cvs/Linux x86_64
Manifest-Sign-Key: 0x761D8E0A
|
|
|
|
|
| |
Package-Manager: portage-2.1.12.2/cvs/Linux ppc64
Manifest-Sign-Key: 0x7194459F
|
|
|
|
| |
Package-Manager: portage-2.2.0_alpha188/cvs/Linux x86_64
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.1/cvs/Linux x86_64
RepoMan-Options: --ignore-arches
Manifest-Sign-Key: 0xA792A613
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0xBEE84C64
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0x62EEF090
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0xBEE84C64
|
|
|
|
|
| |
Package-Manager: portage-2.1.12.2/cvs/Linux i686
Manifest-Sign-Key: 0xC42EB5D6
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0xB9D4F231BD1558AB!
|
|
|
|
|
|
|
| |
again if you run BFQ. Reported by Robert Förster in bug #481820; this didn't appear broken in my tests, but confirmed fix by jlec on IRC so this was probably some specific scenario.
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0x6D34E57D
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0x1F357D42
|
|
|
|
|
| |
Package-Manager: portage-2.1.13.7/cvs/Linux ia64
Manifest-Sign-Key: 0xF6AD3240
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0x6D34E57D
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
|
|
|
|
|
| |
Package-Manager: portage-2.1.12.2/cvs/Linux x86_64
Manifest-Sign-Key: 0xF52D4BBA
|
|
|
|
|
| |
Package-Manager: portage-2.1.12.2/cvs/Linux x86_64
Manifest-Sign-Key: 0xF52D4BBA
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0x6D34E57D
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0x6D34E57D
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
|
|
|
|
|
| |
Package-Manager: portage-2.1.12.2/cvs/Linux x86_64
Manifest-Sign-Key: 0xF52D4BBA
|
|
|
|
|
|
|
| |
NVIDIA users, until fixed; for some users, the 3.10 branch does still appear to be problematic due to an "NVRM: os_pci_init_handle: invalid context!" error. For those that seek more upstream support, this is tracked in NVIDIA internal bug id 1341332 (discovered at https://devtalk.nvidia.com/default/topic/567297/linux/linux-3-10-driver-crash/2/). Thanks for Calchan to report on IRC the ongoing problem(s) that some NVIDIA users are experiencing.
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0x6D34E57D
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0x62EEF090
|
|
|
|
|
|
|
| |
want to switch to the new stable candidate 3.10.7.
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0x6D34E57D
|
|
|
|
|
| |
Package-Manager: portage-2.1.12.2/cvs/Linux x86_64
Manifest-Sign-Key: 0xF52D4BBA
|
|
|
|
|
| |
Package-Manager: portage-2.1.12.2/cvs/Linux x86_64
Manifest-Sign-Key: 0xF52D4BBA
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
RepoMan-Options: --ignore-arches
Manifest-Sign-Key: 0xA792A613
|
|
|
|
|
|
|
| |
grsecurity-2.9.1-2.6.32.61-201308171247
Package-Manager: portage-2.1.12.2/cvs/Linux x86_64
Manifest-Sign-Key: 0xF52D4BBA
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux i686
Manifest-Sign-Key: 0x3C33C650B576E4E3
|
|
|
|
|
|
| |
Signed-off-by: Stratos Psomadakis <psomas@gentoo.org>
Package-Manager: portage-2.1.13.2/cvs/Linux x86_64
Manifest-Sign-Key: 0xBC35D737
|
|
|
|
|
| |
Package-Manager: portage-2.2.0_alpha188/cvs/Linux x86_64
Manifest-Sign-Key: 0xADC916E5
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
|
|
|
|
|
| |
Package-Manager: portage-2.1.13.7/cvs/Linux x86_64
Manifest-Sign-Key: 0x7194459F
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0xFB7C4156
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0xB9D4F231BD1558AB!
|
|
|
|
|
|
|
| |
inconsistent behavior when trying to apply it twice, as it is already applied upstream in 0ac10bd036f0f3b8ce7ac2390446eab9531c72eb; thanks to Bertrand Jacquin (beber) to report this on the gentoo-kernel ML. Since this fixes a build issue, no revision bump is needed; the removal of the inconsistent behavior does in no way change the behavior of the kernel code.
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0x6D34E57D
|
|
|
|
|
|
|
| |
stable candidate. Added patches for a Nouveau build fix as well as enabling TMPFS and DEVTMPFS by default; this behavior alongside an experiment with init system configuration, as well as possible more future behavior can be controlled in a new Gentoo Linux menu.
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0x6D34E57D
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0xB576E4E3
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0xB9D4F231BD1558AB!
|
|
|
|
|
| |
Package-Manager: portage-2.2.0/cvs/Linux x86_64
Manifest-Sign-Key: 0x62EEF090
|
|
|
|
|
| |
Package-Manager: portage-2.1.12.2/cvs/Linux x86_64
Manifest-Sign-Key: 0xF52D4BBA
|
|
|
|
|
| |
Package-Manager: portage-2.2.0_alpha196/cvs/Linux i686
Manifest-Sign-Key: 0x3C33C650B576E4E3
|
|
|
|
|
|
|
| |
versions in LTS due to devaway marked in parentheses, dropped old and broken versions.
Package-Manager: portage-2.1.13.7/cvs/Linux x86_64
Manifest-Sign-Key: 0x6D34E57D
|
|
|
|
| |
Package-Manager: portage-2.1.13.7/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.1.13.7/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.1.13.7/cvs/Linux x86_64
|