From 3b89e1f9621895d5789b024caf93fd3b17654610 Mon Sep 17 00:00:00 2001 From: Peter Krempa Date: Thu, 23 Aug 2018 10:46:39 +0200 Subject: [PATCH] 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 Reviewed-by: Erik Skultety --- 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 52fd50ed36..33d82e6ac6 100644 --- a/docs/api_extension.html.in +++ b/docs/api_extension.html.in @@ -73,9 +73,8 @@

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.