docs: Reword "Preparing Patches" to clarify

Clarify that patches should apply cleanly to the master branch. Give
guidance for typical bug fix process for existing releases.

Signed-off-by: Tim Small <tim@seoss.co.uk>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
Tim Small 2023-07-13 12:00:00 +01:00 committed by Michal Privoznik
parent 3da8d8b5b1
commit 941fc36f11

View File

@ -34,8 +34,10 @@ navigate the code base etc. within most code editors (and IDEs).
Preparing patches
=================
Make sure your patches apply against libvirt git. Developers
only follow git and don't care much about released versions.
Make sure your patches apply against the libvirt git master
branch. The backporting of changes to existing releases is
typically carried out by downstream users at their discretion
after code is merged into the upstream git.
Run the automated tests on your code before submitting any
changes. That is: