1. 29 Jan, 2016 2 commits
  2. 15 Jan, 2016 1 commit
  3. 01 Jan, 2015 3 commits
  4. 30 Dec, 2014 1 commit
  5. 24 Dec, 2014 2 commits
  6. 17 Nov, 2013 2 commits
  7. 29 Oct, 2013 1 commit
  8. 26 Oct, 2013 1 commit
  9. 22 Oct, 2013 1 commit
  10. 18 Oct, 2013 1 commit
  11. 15 Oct, 2013 2 commits
  12. 01 Oct, 2013 1 commit
    • Chris Lalancette's avatar
      Deprecate some old names, and add replacements. · d216bb8b
      Chris Lalancette authored
      We don't really need the _get_ and _set_ on
      the methods that we use; that is implied.  So
      deprecate the methods that are things like
      "max_migration_set_speed" and replace them with
      things like "max_migration_speed=".  Also deprecated
      the "get" in method names.  Also update the
      documentation to mention that these types of names
      are now deprecated.
      Signed-off-by: Chris Lalancette's avatarChris Lalancette <[email protected]>
      d216bb8b
  13. 18 Sep, 2013 1 commit
  14. 09 Sep, 2013 1 commit
  15. 04 Sep, 2013 1 commit
  16. 02 Sep, 2013 1 commit
  17. 28 Aug, 2013 1 commit
  18. 27 Aug, 2013 1 commit
  19. 26 Aug, 2013 2 commits
  20. 13 Aug, 2013 2 commits
  21. 26 Jun, 2011 2 commits
  22. 05 Jan, 2011 1 commit
  23. 12 Dec, 2010 1 commit
    • Chris Lalancette's avatar
      Re-arrange the connect methods. · 0e910727
      Chris Lalancette authored
      Unfortunately, rdoc is pretty stupid and doesn't know how
      to reach across files to generate documentation for methods
      that are in different files from where the class is defined.
      Because of that, we weren't generating the documentation for
      all of the lookup-style and create-style methods (which are
      mostly based off the connection object).  To appease rdoc,
      move any methods hanging off of the connection object into
      connect.c
      Signed-off-by: default avatarChris Lalancette <[email protected]>
      0e910727
  24. 26 Sep, 2010 2 commits
    • Chris Lalancette's avatar
      Much better error reporting. · ed9e5a53
      Chris Lalancette authored
      Previously we were creating error objects with only a
      default string of "Failed to execute function <blah>",
      and placing the actual libvirt error message in the
      exception object in the @libvirt_message member.  However,
      most people never look at @libvirt_message, so the
      default error message is rather useless for figuring out
      why things failed.
      
      With this new patch, we instead put the detailed error
      message in both the @libvirt_message and in the default
      string.  While it does make the default string somewhat
      verbose, it is also much more useful for debugging problems.
      
      While I was at it, I also removed the useless "msg" parameter
      from the create_error function.  Nobody was using it.
      Signed-off-by: default avatarChris Lalancette <[email protected]>
      ed9e5a53
    • Chris Lalancette's avatar
  25. 27 Aug, 2010 2 commits
  26. 15 Jul, 2010 1 commit
  27. 30 Jun, 2010 2 commits