summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorJonathon Jongsma <jjongsma@redhat.com>2021-09-21 14:20:30 -0500
committerJonathon Jongsma <jjongsma@redhat.com>2021-09-21 16:11:07 -0500
commitcd18f4523548e4eebbeae2ff95b7883123cfb85e (patch)
tree84b9ed1b11bc82148f7f0c6f71a30b66c1933603 /README
parent2c9ad18dd19c4889017c82c21c85ed10e82fb03b (diff)
downloadlibvirt-python-cd18f4523548e4eebbeae2ff95b7883123cfb85e.tar.gz
Don't mention email patch submission in README
Since patches are now submitted via gitlab merge requests, don't mention mailing list patch submission in the README. Point to the CONTRIBUTING file instead. Signed-off-by: Jonathon Jongsma <jjongsma@redhat.com>
Diffstat (limited to 'README')
-rw-r--r--README15
1 files changed, 2 insertions, 13 deletions
diff --git a/README b/README
index 8b6f8cb..743c129 100644
--- a/README
+++ b/README
@@ -47,16 +47,5 @@ automate this by using libvirt's run script:
/path/to/libvirt/run python setup.py build
-Patches for this code should be sent to the main libvirt
-development mailing list
-
- http://libvirt.org/contact.html#email
-
-To send patches, it is strongly recommended to use the
-'git send-email' command.
-
-Make sure the mails mention that the patch is for the python
-binding. This can be done by setting a config parameter in the
-local git checkout
-
- git config format.subjectprefix "PATCH python"
+Patches for this code should be submitted as merge requests to the
+project page on gitlab. See CONTRIBUTING.rst for more information.