1. 20 Aug, 2018 1 commit
  2. 06 Aug, 2018 1 commit
  3. 14 Jul, 2018 1 commit
  4. 06 Jul, 2018 4 commits
  5. 31 May, 2018 1 commit
  6. 17 Jan, 2018 1 commit
  7. 29 Dec, 2017 3 commits
  8. 18 Dec, 2017 2 commits
  9. 10 Dec, 2017 1 commit
  10. 01 Dec, 2017 1 commit
  11. 27 Nov, 2017 2 commits
  12. 20 Aug, 2017 1 commit
  13. 10 Aug, 2017 2 commits
  14. 17 Jun, 2017 1 commit
  15. 29 Mar, 2017 2 commits
  16. 01 Dec, 2016 1 commit
  17. 15 Jul, 2016 1 commit
  18. 06 Jul, 2016 1 commit
  19. 13 Jun, 2016 1 commit
  20. 25 Apr, 2016 2 commits
  21. 06 Apr, 2016 1 commit
  22. 03 Apr, 2016 1 commit
  23. 22 Mar, 2016 1 commit
  24. 17 Mar, 2016 1 commit
  25. 15 Mar, 2016 1 commit
    • Thijs Kinkhorst's avatar
      Disable table with fixed version per suite. · d746f81d
      Thijs Kinkhorst authored
      This is often very confusing because it lists the state only for the main
      archive, not the security archive, so stable will be shown as vulnerable
      for many weeks after a DSA has been issued, until the next point release.
      That's not very relevant information. It also duplicates the table below
      with fixed status per suite and archive.
      
      
      git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@40387 e39458fd-73e7-0310-bf30-c45bca0a0e42
      d746f81d
  26. 02 Mar, 2016 1 commit
  27. 01 Feb, 2016 3 commits
  28. 30 Jan, 2016 1 commit