From bd4f4d168660f563435968207fc36dad7c8c9e46 Mon Sep 17 00:00:00 2001 From: Andrea Bolognani Date: Wed, 4 Jan 2017 12:14:13 +0100 Subject: [PATCH] docs: Add missing

elements Some of the

  • elements in the "General tips for contributing patches" section were missing the corresponding inner

    element, so they ended up all lumped together. --- docs/hacking.html.in | 25 +++++++++++++++++-------- 1 file changed, 17 insertions(+), 8 deletions(-) diff --git a/docs/hacking.html.in b/docs/hacking.html.in index 5f19143408..13b3640259 100644 --- a/docs/hacking.html.in +++ b/docs/hacking.html.in @@ -8,20 +8,26 @@

    General tips for contributing patches

      -
    1. Discuss any large changes on the mailing list first. Post patches - early and listen to feedback.
    2. +
    3. +

      Discuss any large changes on the mailing list first. Post patches + early and listen to feedback.

      +
    4. -
    5. Official upstream repository is kept in git +
    6. +

      Official upstream repository is kept in git (git://libvirt.org/libvirt.git) and is browsable along with other libvirt-related repositories - (e.g. libvirt-python) online.

    7. + (e.g. libvirt-python) online.

      + -
    8. Patches to translations are maintained via +
    9. +

      Patches to translations are maintained via the zanata project. If you want to fix a translation in a .po file, join the appropriate language team. The libvirt release process automatically pulls the latest version of each translation - file from zanata.

    10. + file from zanata.

      +
    11. Post patches using "git send-email", with git rename detection enabled. You need a one-time setup of:

      @@ -98,8 +104,11 @@ of git bisect, among other things).

    12. -
    13. Make sure your patches apply against libvirt GIT. Developers - only follow GIT and don't care much about released versions.
    14. +
    15. +

      Make sure your patches apply against libvirt GIT. Developers + only follow GIT and don't care much about released versions.

      +
    16. +
    17. Run the automated tests on your code before submitting any changes. In particular, configure with compile warnings set to -Werror. This is done automatically for a git checkout; from a -- GitLab