[libvirt PATCH 06/10] docs: Reword "Preparing Patches" to clarify

[Tim Small]

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 at seoss.co.uk>
---
 docs/hacking.rst | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/hacking.rst b/docs/hacking.rst
index 11cd21223a..85918c9176 100644
--- a/docs/hacking.rst
+++ b/docs/hacking.rst
@@ -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:
-- 
2.39.2