1. 19 Jan, 2021 1 commit
    • Erik Skultety's avatar
      ci: Refresh Dockerfiles · 274972df
      Erik Skultety authored
      Changes contained in this refresh:
      - CentOS 7 is pulled from docker.io registry
      - PowerTools repo name regression fix for CentOS Stream
      - enhancement for the workaround fix for JDK installation fails on Debian 10
        '-slim' containers
      Signed-off-by: Erik Skultety's avatarErik Skultety <eskultet@redhat.com>
  2. 01 Dec, 2020 3 commits
  3. 23 Nov, 2020 1 commit
  4. 03 Nov, 2020 1 commit
  5. 04 Aug, 2020 1 commit
  6. 15 May, 2020 3 commits
  7. 30 Apr, 2020 1 commit
  8. 07 Apr, 2020 1 commit
    • Daniel P. Berrangé's avatar
      github: enable lockdown of issues and merge requests · 0c7ca057
      Daniel P. Berrangé 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...
  9. 16 Jan, 2020 1 commit
  10. 24 Apr, 2018 1 commit
    • Daniel P. Berrangé's avatar
      git: add config file telling git-publish how to send patches · 90f950c8
      Daniel P. Berrangé 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 P. Berrangé's avatarDaniel P. Berrangé <berrange@redhat.com>
  11. 15 Jul, 2011 1 commit
  12. 17 Jun, 2011 1 commit
  13. 16 Dec, 2010 3 commits
  14. 29 Nov, 2010 3 commits
  15. 15 Nov, 2010 1 commit
  16. 10 Nov, 2010 6 commits
  17. 29 Oct, 2010 1 commit
  18. 27 Oct, 2010 2 commits
  19. 20 Oct, 2010 5 commits
  20. 18 Oct, 2010 1 commit
  21. 05 Oct, 2010 1 commit