Commit message (Expand) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Stable for amd64, wrt bug #418341 | 2012-05-31 | 1 | -2/+16 | |
* | Stable for amd64, wrt bug #418341 | 2012-05-31 | 2 | -3/+6 | |
* | marked x86 per bug 348594 | 2012-05-31 | 1 | -16/+2 | |
* | marked x86 per bug 348594 | 2012-05-31 | 2 | -3/+6 | |
* | docs dir was renamed to manual. #418257 | 2012-05-30 | 1 | -9/+9 | |
* | docs dir was renamed to manual. #418257 | 2012-05-30 | 2 | -3/+6 | |
* | Stable for amd64, wrt bug #348594 | 2012-05-30 | 1 | -10/+10 | |
* | Stable for amd64, wrt bug #348594 | 2012-05-30 | 2 | -3/+6 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+10 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+71 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+37 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+20 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+39 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+23 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+19 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+21 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+19 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+27 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+22 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+20 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+20 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+26 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+22 | |
* | sign Manifest | 2012-05-30 | 1 | -0/+14 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+22 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+21 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+22 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+30 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+22 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 2 | -1/+27 | |
* | Security bump. CVE-2012-2098 #417909 | 2012-05-30 | 1 | -9/+12 |