1. 15 May, 2020 4 commits
  2. 30 Apr, 2020 1 commit
  3. 07 Apr, 2020 1 commit
    • Daniel Berrange's avatar
      github: enable lockdown of issues and merge requests · 5e172b32
      Daniel Berrange authored
      Libvirt uses GitHub as an automated read-only mirror. The goals were to
      have a disaster recovery backup for libvirt.org, a way to make it easy
      for people to clone their own private copy of libvirt Git, and finally
      as a way to interact with apps like Travis.
      The project description was set to a message telling people that we
      don't respond to pull requests. This was quite a negative message to
      potential contributors, and also did not give them any guidance about
      the right way to submit to libvirt. Many also missed the description and
      submitted issues or pull requests regardless.
      It is possible to disable the issue tracker in GitHub, but there is no
      way to disable merge requests. Disabling the issue tracker would also
      leave the problem of users not being given any positive information
      about where they should be reporting instead.
      There is a fairly new 3rd party application built for GitHub that
      provides a bot which auto-responds to both issues and merge requests,
      closing and locking them, with a arbitrary comment:
      This commit adds a suitable configuration file for libvirt, which
      tries to give a positive response to user's issue/pullreq and guide
      them to the desired contribution path on GitLab.
      Reviewed-by: Andrea Bolognani's avatarAndrea Bolognani <[email protected]>
      Reviewed-by: Pavel Hrdina's avatarPavel Hrdina <[email protected]>
      Reviewed-by: Eric Blake's avatarEric Blake <[email protected]>
      Signed-off-by: Daniel Berrange's avatarDaniel P. Berrangé <[email protected]>
  4. 21 Feb, 2020 1 commit
  5. 23 Nov, 2019 1 commit
  6. 24 Apr, 2018 1 commit
    • Daniel Berrange's avatar
      git: add config file telling git-publish how to send patches · 9f71ff5a
      Daniel Berrange authored
      The "git-publish" tool is a useful git extension for sending patch
      series for code review. It automatically creates versioned tags
      each time code on a branch is sent, so that there is a record of
      each version. It also remembers the cover letter so it does not
      need re-entering each time the series is reposted.
      With this config file present it is now sufficient[1] to run
        $ git publish
      to send all patches in a branch to the list for review, with the
      correct subject prefix added for this non-core libvirt module.
      [1] Assuming your $HOME/.gitconfig has an SMTP server listed
      at least e.g.
              smtpserver = smtp.example.com
      Signed-off-by: Daniel Berrange's avatarDaniel P. Berrangé <[email protected]>
  7. 18 Feb, 2018 3 commits
  8. 17 Feb, 2018 1 commit
  9. 11 Feb, 2018 1 commit
  10. 22 Sep, 2016 2 commits
  11. 13 Jun, 2016 2 commits
  12. 10 Jun, 2016 1 commit
    • Guido Günther's avatar
      Don't make volume upload zero bytes · 03f18670
      Guido Günther authored
      The virStreamSourceFunc internal_sendall currently returns the first
      value passed in from the block, which according the ruby-libvirt docs
      should be zero:
        The send block should return an array of 2 elements; the first element
        should be the return code from the block (-1 for error, 0 otherwise)
      But according to the libvirt docs of virStreamSourceFunc this indicates
        Returns:  the number of bytes filled, 0 upon end of file, or -1 upon error
      So return the size of the buffer to unbreak volume uploads.
  13. 07 Feb, 2016 1 commit
  14. 29 Jan, 2016 7 commits
  15. 28 Jan, 2016 2 commits
  16. 15 Jan, 2016 1 commit
  17. 20 Nov, 2015 3 commits
  18. 04 Jan, 2015 2 commits
  19. 01 Jan, 2015 5 commits