diff --git a/HACKING b/HACKING
index 0aba279bf7..36564118e5 100644
--- a/HACKING
+++ b/HACKING
@@ -23,19 +23,11 @@ libvirt-python) online .
join the appropriate language team. The libvirt release process automatically
pulls the latest version of each translation file from zanata.
-(4) Post patches in unified diff format, with git rename detection enabled. You
+(4) Post patches using "git send-email", with git rename detection enabled. You
need a one-time setup of:
git config diff.renames true
-After that, a command similar to this should work:
-
- diff -urp libvirt.orig/ libvirt.modified/ > libvirt-myfeature.patch
-
-or:
-
- git diff > libvirt-myfeature.patch
-
Also, for code motion patches, you may find that "git diff --patience"
provides an easier-to-read patch. However, the usual workflow of libvirt
developer is:
diff --git a/docs/hacking.html.in b/docs/hacking.html.in
index a471d88552..5f19143408 100644
--- a/docs/hacking.html.in
+++ b/docs/hacking.html.in
@@ -23,20 +23,10 @@
automatically pulls the latest version of each translation
file from zanata.
-
Post patches in unified diff format, with git rename
+
Post patches using "git send-email", with git rename
detection enabled. You need a one-time setup of:
git config diff.renames true
-
- After that, a command similar to this should work:
-
- diff -urp libvirt.orig/ libvirt.modified/ > libvirt-myfeature.patch
-
-
- or:
-
-
- git diff > libvirt-myfeature.patch
Also, for code motion patches, you may find that git
diff --patience
provides an easier-to-read patch.