From 2825803477a54a337e194288ae6a8fd1c950957c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A1n=20Tomko?= Date: Fri, 18 Oct 2019 22:55:05 +0200 Subject: [PATCH] docs: hacking: mention git-publish prominently MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This tool takes care of many of the tedious parts of submitting a patch. Mention it first, above the "manual" way using git send-email. Signed-off-by: Ján Tomko Reviewed-by: Daniel P. Berrangé Reviewed-by: Andrea Bolognani --- docs/hacking.html.in | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/hacking.html.in b/docs/hacking.html.in index 1da2cbbd9f..42c8596abe 100644 --- a/docs/hacking.html.in +++ b/docs/hacking.html.in @@ -29,7 +29,11 @@ file from zanata.

-

  • Post patches using git send-email.

    +

  • The simplest way to send patches is to use the + git-publish + tool. All libvirt-related repositories contain a config file that + tells git-publish to use the correct mailing list and subject prefix.

    +

    Alternatively, you may send patches using git send-email.

    Also, for code motion patches, you may find that git diff --patience provides an easier-to-read patch. However, the usual workflow of libvirt developer is:

    -- GitLab