docs: api_extension: Don't encourage other tools than git

Save us hassle in the list if anybody would read this.

Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Erik Skultety <eskultet@redhat.com>

diff --git a/docs/api_extension.html.in b/docs/api_extension.html.in
index 52fd50ed369fb6731a2d126fee4d5b869212a7cc..33d82e6ac6f71cf6c7b4cd7048ff22789aed4c2e 100644 (file)
--- 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.