Save us hassle in the list if anybody would read this.
Signed-off-by: Peter Krempa <pkrempa@redhat.com>
---
docs/api_extension.html.in | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/docs/api_extension.html.in b/docs/api_extension.html.in
index b473d09b17..d2c7fd6cfb 100644
--- a/docs/api_extension.html.in
+++ b/docs/api_extension.html.in
@@ -73,9 +73,8 @@
<p>
Submit new code in the form of one patch per step. That's not to say
submit patches before you have working functionality--get the whole thing
- working and make sure you're happy with it. Then use git or some other
- version control system that lets you rewrite your commit history and
- break patches into pieces so you don't drop a big blob of code on the
+ working and make sure you're happy with it. Then use git to break the
+ changes into pieces so you don't drop a big blob of code on the
mailing list in one go. Also, you should follow the upstream tree, and
rebase your series to adapt your patches to work with any other changes
that were accepted upstream during your development.
--
2.16.2
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list