1
0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-03-16 18:50:18 +03:00

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>
This commit is contained in:
Peter Krempa 2018-08-23 10:46:39 +02:00
parent 6be034a8c0
commit 3b89e1f962

View File

@ -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.