1. 15 Mar, 2017 1 commit
  2. 12 Mar, 2017 1 commit
  3. 11 Mar, 2017 9 commits
  4. 10 Mar, 2017 2 commits
  5. 06 Mar, 2017 1 commit
  6. 04 Mar, 2017 4 commits
  7. 27 Feb, 2017 1 commit
  8. 26 Feb, 2017 1 commit
  9. 24 Feb, 2017 2 commits
  10. 15 Feb, 2017 1 commit
  11. 11 Feb, 2017 1 commit
  12. 08 Feb, 2017 1 commit
    • Sébastien Wilmet's avatar
      TemplatesPersonal: fix for loop condition with G_MAXINT · 9d2ff01c
      Sébastien Wilmet authored
      The condition was always true, even after overflow. What we want to
      avoid is negative numbers. So stop the loop at G_MAXINT.
      
      It is anyway extremely unlikely that someone has that many personal
      templates, so the bug never happened in practice.
      
      Found by Coverity.
      9d2ff01c
  13. 07 Feb, 2017 3 commits
  14. 06 Feb, 2017 1 commit
  15. 04 Feb, 2017 1 commit
  16. 30 Jan, 2017 1 commit
  17. 26 Jan, 2017 5 commits
  18. 18 Jan, 2017 2 commits
    • Sébastien Wilmet's avatar
      News: add news for release 3.22.1 · 060081a8
      Sébastien Wilmet authored
      The release was created in a side-branch. From now on, I'll try to keep
      the NEWS file complete on the master branch, to have a good history
      overview.
      060081a8
    • Sébastien Wilmet's avatar
      Add release dates to the NEWS file · 94e43692
      Sébastien Wilmet authored
      I think it's useful information. It can be retrieved from git, but to do
      it correctly (get the commiter date of the commit that the git tag
      points to) is more difficult. It's easier if it's present in the NEWS
      file.
      
      The dates have been added with this quick and dirty script:
      ```
      	#!/usr/bin/env bash
      
      	tags_list=`git tag`
      	for tag in $tags_list
      	do
      		# For the date, it takes the commiter date of the git commit that $tag
      		# points to. This is normally the closest date to the real date of the
      		# release (if the tag refers to a version). Sometimes a maintainer
      		# forgets to create the tag and the tag is created afterwards.
      		#
      		# To show git tags alongside the tag creation dates, use the following
      		# command instead:
      		# $ git tag -l --format="%(refname:strip=2) - %(taggerdate:short)"
      
      		commiter_date=`git log -1 --date=short --pretty="format:%cd" $tag`
      
      		sed -i "s/^\(Release ${tag#v}\)$/\1, ${commiter_date}/" NEWS
      	done
      
      	sed -i "s/\(--------\)/\1------------/" NEWS
      ```
      
      For the versions <= 0.2, the dates have been added manually from the
      information in the first git repo (no longer public).
      94e43692
  19. 28 Dec, 2016 1 commit
  20. 25 Dec, 2016 1 commit