1. 12 Feb, 2019 1 commit
  2. 20 Aug, 2018 1 commit
  3. 06 Aug, 2018 1 commit
  4. 14 Jul, 2018 1 commit
  5. 06 Jul, 2018 4 commits
  6. 31 May, 2018 1 commit
  7. 17 Jan, 2018 1 commit
  8. 29 Dec, 2017 3 commits
  9. 18 Dec, 2017 2 commits
  10. 10 Dec, 2017 1 commit
  11. 01 Dec, 2017 1 commit
  12. 27 Nov, 2017 2 commits
  13. 20 Aug, 2017 1 commit
  14. 10 Aug, 2017 2 commits
  15. 17 Jun, 2017 1 commit
  16. 29 Mar, 2017 2 commits
  17. 01 Dec, 2016 1 commit
  18. 15 Jul, 2016 1 commit
  19. 06 Jul, 2016 1 commit
  20. 13 Jun, 2016 1 commit
  21. 25 Apr, 2016 2 commits
  22. 06 Apr, 2016 1 commit
  23. 03 Apr, 2016 1 commit
  24. 22 Mar, 2016 1 commit
  25. 17 Mar, 2016 1 commit
  26. 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
  27. 02 Mar, 2016 1 commit
  28. 01 Feb, 2016 3 commits