1. 26 Apr, 2019 4 commits
  2. 04 Dec, 2018 1 commit
  3. 29 Aug, 2018 1 commit
  4. 26 Feb, 2018 1 commit
  5. 05 Feb, 2018 1 commit
  6. 09 Nov, 2017 1 commit
  7. 03 Oct, 2017 1 commit
  8. 19 Jul, 2017 1 commit
  9. 12 Jul, 2017 1 commit
  10. 30 Nov, 2016 1 commit
  11. 21 Sep, 2016 1 commit
  12. 11 Aug, 2016 1 commit
  13. 10 Aug, 2016 2 commits
  14. 02 Aug, 2016 1 commit
  15. 10 Jun, 2016 1 commit
  16. 08 Feb, 2016 1 commit
  17. 20 Jan, 2016 1 commit
  18. 19 Feb, 2015 1 commit
  19. 31 Jul, 2014 2 commits
  20. 25 Jul, 2014 1 commit
  21. 20 Jun, 2014 1 commit
  22. 29 May, 2014 1 commit
  23. 26 May, 2014 1 commit
  24. 16 May, 2014 1 commit
  25. 06 May, 2014 1 commit
  26. 05 May, 2014 1 commit
  27. 02 May, 2014 3 commits
  28. 30 Apr, 2014 1 commit
  29. 29 Apr, 2014 1 commit
  30. 24 Apr, 2014 2 commits
  31. 16 Apr, 2014 1 commit
  32. 04 Apr, 2014 1 commit
    • Jan Kadlec's avatar
      new_node: Do not reuse old pointers in zone copy. · 63384e60
      Jan Kadlec authored
       - node->new_node is thus obosolete.
       - since hattrie_dup made almost a full copy anyway, it's feasible to
         let the zone contents recreate the zone anew, with proper pointers.
      (new node was used to set only parent pointer, others were reset anyway
      in adjusting, all this will die in the new zone API, but at least like
      this it's easier to maintain.)
      63384e60