1. 20 Mar, 2019 1 commit
  2. 19 Mar, 2019 1 commit
  3. 06 Mar, 2019 1 commit
  4. 26 Feb, 2019 1 commit
  5. 25 Feb, 2019 2 commits
  6. 22 Feb, 2019 1 commit
  7. 21 Feb, 2019 1 commit
  8. 12 Feb, 2019 1 commit
  9. 31 Jan, 2019 1 commit
  10. 28 Jan, 2019 1 commit
  11. 24 Jan, 2019 1 commit
  12. 21 Jan, 2019 2 commits
  13. 17 Jan, 2019 3 commits
  14. 15 Jan, 2019 1 commit
  15. 09 Jan, 2019 1 commit
  16. 03 Jan, 2019 1 commit
  17. 02 Jan, 2019 2 commits
  18. 31 Dec, 2018 1 commit
  19. 19 Dec, 2018 1 commit
  20. 18 Dec, 2018 5 commits
  21. 07 Dec, 2018 1 commit
  22. 19 Nov, 2018 1 commit
  23. 14 Nov, 2018 2 commits
    • Libor Peltan's avatar
      doc: fixed journal-contentS · 2bc9fa31
      Libor Peltan authored
      2bc9fa31
    • Daniel Kahn Gillmor's avatar
      docs: manually set copyright year in doc/conf.py · 476ae2b9
      Daniel Kahn Gillmor authored
      To make builds bit-by-bit reproducible, the source code should not
      change what is built based on the current time.
      
      Currently, the documentation sets its build year by querying the
      system clock, which means that the produced documentation changes when
      you build it in a different year.
      
      This approach costs one manual commit per year of development, but
      always builds the same thing, and claims no additional copyright years
      if no changes have been made to the source.
      
      It provides a nice warning so that (hopefully) someone building the
      package which needs the manual year update should notice and can make
      the update themselves if the source code is actually active (as i
      expect it to be in 2020, but who knows what will happen in 2035?)
      
      Compare with the use of SOURCE_DATE_EPOCH:
      !951
      476ae2b9
  24. 12 Nov, 2018 1 commit
  25. 08 Nov, 2018 1 commit
  26. 07 Nov, 2018 1 commit
  27. 06 Nov, 2018 1 commit
  28. 05 Nov, 2018 3 commits