1. 06 Sep, 2016 2 commits
  2. 04 Sep, 2016 2 commits
  3. 02 Sep, 2016 1 commit
  4. 29 Aug, 2016 1 commit
  5. 28 Aug, 2016 1 commit
  6. 26 Aug, 2016 2 commits
  7. 23 Aug, 2016 1 commit
  8. 22 Aug, 2016 1 commit
  9. 08 Jun, 2016 2 commits
  10. 07 Jun, 2016 3 commits
  11. 30 May, 2016 1 commit
  12. 22 May, 2016 1 commit
    • Son Nguyen's avatar
      Add more translations from Launchpad.net · 45658b86
      Son Nguyen authored
      - Chinese Traditional - zh_CN
      - Indonesia - id
      - Estonia - et
      - Kannada - kn
      - Mongola - mn
      - Persian - fa
      - Polish - pl
      - Romanian - ro
      - Serbian - sr
      - Thai - th
      - Turkish - tr
      - Ukrainian - uk
      - Hungarian - hu
      
      Change-Id: I31d85f9525762d724e8dd426dc4a5ba08e7dd285
      45658b86
  13. 02 May, 2016 1 commit
  14. 11 Apr, 2016 5 commits
  15. 10 Mar, 2016 3 commits
  16. 09 Mar, 2016 2 commits
  17. 08 Mar, 2016 3 commits
  18. 07 Mar, 2016 4 commits
  19. 26 Jan, 2016 2 commits
  20. 09 Dec, 2015 1 commit
  21. 01 Dec, 2015 1 commit
    • Aaron Wells's avatar
      Patching lptools to send the auto-generated release files · 9d445a56
      Aaron Wells authored
      We were *always* getting prompted for the changes & releasenotes
      three times on each release. That's because the optional lptools
      arguments for change & release notes must be the 5th and 6th.
      But, we couldn't provide them, because the lptools 4th optional
      argument is "new milestone", and if you try to provide one that
      already exists, it errors out.
      
      So, we had to leave "new milestone" empty, and that meant we
      also had to leave change & release notes empty.
      
      Rather than getting deep into the logic of the lptools utility,
      I just patched is so that it always skips the "new milestone"
      argument.
      9d445a56