1. 17 Mar, 2022 2 commits
  2. 20 Oct, 2021 1 commit
  3. 03 Sep, 2021 4 commits
  4. 27 Jul, 2021 1 commit
    • Daniel P. Berrangé's avatar
      gitlab: use custom docker:dind image · 4956432d
      Daniel P. Berrangé authored
      The current docker:dind container has broken default seccomp filter that
      results in clone3 being blocked, which in turn breaks Fedora 35 rawhide.
      This custom image has a workaround that causes the seccomp filter to
      return ENOSYS for clone3 instad of EPERM, thus triggering glibc to
      fallback to clone correctly.
      Signed-off-by: Daniel P. Berrangé's avatarDaniel P. Berrangé <berrange@redhat.com>
  5. 19 Jan, 2021 1 commit
    • Erik Skultety's avatar
      ci: Refresh Dockerfiles · f8bb081c
      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>
  6. 01 Dec, 2020 3 commits
  7. 25 Jun, 2020 3 commits
  8. 30 Apr, 2020 1 commit
  9. 07 Apr, 2020 1 commit
    • Daniel P. Berrangé's avatar
      github: enable lockdown of issues and merge requests · fefdfbb2
      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 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 <abologna@redhat.com>
      Reviewed-by: Pavel Hrdina's avatarPavel Hrdina <phrdina@redhat.com>
      Reviewed-by: Eric Blake's avatarEric Blake <eblake@redhat.com>
      Signed-off-by: Daniel P. Berrangé's avatarDaniel P. Berrangé <berrange@redhat.com>
  10. 16 Jan, 2020 1 commit
  11. 24 Apr, 2018 1 commit
    • Daniel P. Berrangé's avatar
      git: add config file telling git-publish how to send patches · 4fc0f5ef
      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>
  12. 10 Feb, 2011 3 commits
  13. 13 Nov, 2010 1 commit
  14. 16 Aug, 2010 1 commit
  15. 25 Jan, 2010 1 commit
  16. 17 Nov, 2009 5 commits