1. 08 Nov, 2018 1 commit
  2. 16 Oct, 2018 2 commits
  3. 10 Aug, 2017 1 commit
    • Tomek Mrugalski's avatar
      [5314] Empty status added · b0572c95
      Tomek Mrugalski authored
       - it's a copy 5272 code added that's already on master,
         but it seems easier to add it on a branch than go through
         the whole rebase process.
      b0572c95
  4. 01 Aug, 2017 1 commit
  5. 29 Mar, 2017 1 commit
  6. 17 Mar, 2017 1 commit
  7. 17 Feb, 2017 1 commit
  8. 24 Jan, 2017 1 commit
  9. 14 Dec, 2016 1 commit
  10. 16 Dec, 2015 2 commits
  11. 10 Jun, 2015 1 commit
  12. 09 Jun, 2015 2 commits
  13. 20 May, 2015 1 commit
  14. 19 May, 2015 2 commits
  15. 06 Sep, 2013 2 commits
  16. 05 Sep, 2013 2 commits
  17. 12 Jul, 2013 2 commits
  18. 23 May, 2013 2 commits
  19. 22 May, 2013 1 commit
  20. 20 May, 2013 1 commit
  21. 09 Apr, 2013 1 commit
  22. 27 Mar, 2013 1 commit
  23. 19 Mar, 2013 1 commit
  24. 06 Mar, 2013 1 commit
  25. 22 Feb, 2013 1 commit
  26. 20 Feb, 2013 1 commit
  27. 18 Feb, 2013 1 commit
  28. 25 Oct, 2012 1 commit
  29. 11 Oct, 2012 1 commit
    • JINMEI Tatuya's avatar
      [2203] changed the callback type of addRemoteConfig to boost::function. · da22b377
      JINMEI Tatuya authored
      this will make it more convenient, e.g., by allowing the caller to pass
      boost::bind encapsulating a class object and a class method.
      
      boost::function is upper compatible to function pointer, so it doesn't
      ensure source-level compatibility.
      
      the functor overhead shouldn't matter in this context, and since this module
      already uses boost::function this change doesn't introduce additional
      dependency.
      da22b377
  30. 03 Oct, 2012 1 commit
    • JINMEI Tatuya's avatar
      [2203] changed the callback type of addRemoteConfig to boost::function. · 4fa694db
      JINMEI Tatuya authored
      this will make it more convenient, e.g., by allowing the caller to pass
      boost::bind encapsulating a class object and a class method.
      
      boost::function is upper compatible to function pointer, so it doesn't
      ensure source-level compatibility.
      
      the functor overhead shouldn't matter in this context, and since this module
      already uses boost::function this change doesn't introduce additional
      dependency.
      4fa694db
  31. 18 May, 2012 1 commit
  32. 17 May, 2012 1 commit