From: Tim Small Date: Thu, 13 Jul 2023 11:00:00 +0000 (+0100) Subject: docs: Reword "Preparing Patches" to clarify X-Git-Tag: v9.6.0-rc1~79 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=941fc36f114e6581425310462bd148b924d99495;p=thirdparty%2Flibvirt.git 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 Reviewed-by: Michal Privoznik --- 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: