From patchwork Tue Nov 22 09:56:05 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?q?Alex_Benn=C3=A9e?= X-Patchwork-Id: 627498 Delivered-To: patch@linaro.org Received: by 2002:a17:522:c983:b0:460:3032:e3c4 with SMTP id kr3csp2344284pvb; Tue, 22 Nov 2022 01:56:37 -0800 (PST) X-Google-Smtp-Source: AA0mqf7Ye+epuEFro9iYSgBSceFfcqAqAPpiMVM1YR7bon34fI6QeeNX/OMtkXo6NetHGlUxAadt X-Received: by 2002:a05:620a:146b:b0:6fa:f548:7cfd with SMTP id j11-20020a05620a146b00b006faf5487cfdmr4107916qkl.103.1669110997644; Tue, 22 Nov 2022 01:56:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669110997; cv=none; d=google.com; s=arc-20160816; b=Nk9k/krudyyA8xhL0n0/Izxga6k93dd2NB2owr+cf5bgxBxhTZmC8LvTYCmtTfnqhw NoPCOl0ov2IADMWzA0UhwAZYVfbWKDGuWckQjhs6Bc00GfOtRden4BZM9BfcMI/2b4C6 eFZ2EsDK1tHlmjlDIZdQSAo4sFaNgbrTMhS+rcQZhFZ6ubd1P8qfhwILjnsCq5/P0muX zjaZ/w+TwZEtjD1P63dnOEy7PS2mV9HDTNSXtOWopByhcQ1b4D6oEyBtd6CneCnBPLyf 4DF2Zv7Hj/tQz5BahtEH+qLY/w1Yj0DcF3iytWy5lGHZA/oTG2D5CaAq2ucVYG8qpPFF gBTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=sender:errors-to:list-subscribe:list-help:list-post:list-archive :list-unsubscribe:list-id:precedence:content-transfer-encoding :mime-version:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=noAWK4Tr2C3oo56ITKJfPI3QYAkN6x1CbswUT/w7uoM=; b=OQOS+mjRsQtVFjDm8cj7YjXkFrUYnzWIBtEBXGRNNGKEgY5OgCXjd86KT5yy8ucaQZ zF8ekqsqNC7toDe4YsaxP5KfjUXcPh8MCQq2DvXl2EYw5NLhoZZTEZDGZ89rceKt/8dX WzTjnL4KeeQoPhyLgWajhBXHk8w1uK/S8CR0KilRaCDZoXNR6tYhunEvwymNp4lrXQZQ 9vba23Ne2qjgLHbDA7/HACpE/MNiI+d67PPS43OLZ2O7Qalk6pIWsLDjopSbZrAV+4Ps LThsM8NHhpn8ow3TH6ajwJdSsmAGMG+LP0AaCvhTCNu7nkugFmhDkMmgh+ieBJVnCtVp 9O7A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=kEGqoUow; spf=pass (google.com: domain of qemu-devel-bounces+patch=linaro.org@nongnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom="qemu-devel-bounces+patch=linaro.org@nongnu.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from lists.gnu.org (lists.gnu.org. [209.51.188.17]) by mx.google.com with ESMTPS id r8-20020ae9d608000000b006eecf6a0862si7725807qkk.547.2022.11.22.01.56.37 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Tue, 22 Nov 2022 01:56:37 -0800 (PST) Received-SPF: pass (google.com: domain of qemu-devel-bounces+patch=linaro.org@nongnu.org designates 209.51.188.17 as permitted sender) client-ip=209.51.188.17; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=kEGqoUow; spf=pass (google.com: domain of qemu-devel-bounces+patch=linaro.org@nongnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom="qemu-devel-bounces+patch=linaro.org@nongnu.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oxQ0r-0002Rm-Hr; Tue, 22 Nov 2022 04:56:21 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oxQ0p-0002Lj-9L for qemu-devel@nongnu.org; Tue, 22 Nov 2022 04:56:19 -0500 Received: from mail-wr1-x42b.google.com ([2a00:1450:4864:20::42b]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oxQ0n-0003sF-6w for qemu-devel@nongnu.org; Tue, 22 Nov 2022 04:56:19 -0500 Received: by mail-wr1-x42b.google.com with SMTP id n3so7318825wrp.5 for ; Tue, 22 Nov 2022 01:56:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=noAWK4Tr2C3oo56ITKJfPI3QYAkN6x1CbswUT/w7uoM=; b=kEGqoUowkhR9NjDmEdDbwWqRTfoinf+M4aMTW+PMyzv2y7tGA6WlCA9Dov0aWN8dj4 IHlhW11nOMstUGKXOhaB0/vBQFZQ8QQxohmwnLtW4wSedHfDXqivB1Z1iwxYhWlGsoRL 7j/HCYMVJSrdM6qKWClMxdW5pV0tH5BI9ODS2EM1H4FjeXdRa4I09Y63+1szoUWafCxh dFx4js+rSQrsoMYtNep1jBJ+lsowGGOl/aFeXCBRaRMiyas/5nsuODpRaf4fRKRTpmug 9cZVZlC/COr/LzNAM5s/73U+uoXhOncOyvcr6Z9P+RAnuramo4kT0kF/F8eWpczrcE4O 4vhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=noAWK4Tr2C3oo56ITKJfPI3QYAkN6x1CbswUT/w7uoM=; b=cwy8MciveAElifkxTgknAEAoFbv1IFWmZV6ctVLeBtFfP3fm8R9O5fFrASpjkNRom9 60TlE2UR/5IkieQw/j56PLu5QwImXyYNb+Y9hVWeGQo098CacDJQF81v97RcVda8wJZH QogLwPEYTw7BKR/OqH7bIaaV1AdKMjfCY8Oqr0v5edu4y0yvQDZqXAQQvFzVgBbilSQY GIZY9noLvnPCEjnn8Mn8IhoXxFUN9/vi0evLMi0m6z9gcYBLPFxAzK0e9AuRSrhOuHrc D9Qtd2B9IBatZAMMiQExEum3gxi9yOg5YtgYTF7Izvilp8HxRGrYsw7+v5i32pz6v7bk ij3g== X-Gm-Message-State: ANoB5pkj8JEUdh5oiwREkRvUuC786qYSVj6P3F/Wbq4gzpPJLb+Ui1hw SFLiIse30baPQFbhSPXDtfGcng== X-Received: by 2002:adf:d841:0:b0:236:5655:13a5 with SMTP id k1-20020adfd841000000b00236565513a5mr13405199wrl.477.1669110975720; Tue, 22 Nov 2022 01:56:15 -0800 (PST) Received: from zen.linaroharston ([185.81.254.11]) by smtp.gmail.com with ESMTPSA id d16-20020a5d6dd0000000b0022584c82c80sm13391628wrz.19.2022.11.22.01.56.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Nov 2022 01:56:13 -0800 (PST) Received: from zen.lan (localhost [127.0.0.1]) by zen.linaroharston (Postfix) with ESMTP id 264311FFBE; Tue, 22 Nov 2022 09:56:11 +0000 (GMT) From: =?utf-8?q?Alex_Benn=C3=A9e?= To: qemu-devel@nongnu.org Cc: stefanha@redhat.com, =?utf-8?q?Alex_Benn=C3=A9e?= , Paolo Bonzini , =?utf-8?q?Philippe_Mathieu-Daud=C3=A9?= Subject: [PULL v2 06/11] docs/devel: simplify the minimal checklist Date: Tue, 22 Nov 2022 09:56:05 +0000 Message-Id: <20221122095610.3343175-7-alex.bennee@linaro.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20221122095610.3343175-1-alex.bennee@linaro.org> References: <20221122095610.3343175-1-alex.bennee@linaro.org> MIME-Version: 1.0 Received-SPF: pass client-ip=2a00:1450:4864:20::42b; envelope-from=alex.bennee@linaro.org; helo=mail-wr1-x42b.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+patch=linaro.org@nongnu.org Sender: qemu-devel-bounces+patch=linaro.org@nongnu.org The bullet points are quite long and contain process tips. Move those bits of the bullet to the relevant sections and link to them. Use a table for nicer formatting of the checklist. Signed-off-by: Alex Bennée Reviewed-by: Stefan Hajnoczi Reviewed-by: Paolo Bonzini Reviewed-by: Philippe Mathieu-Daudé Message-Id: <20221117172532.538149-7-alex.bennee@linaro.org> diff --git a/docs/devel/submitting-a-patch.rst b/docs/devel/submitting-a-patch.rst index 1319dfd3c2..b2a162ff4c 100644 --- a/docs/devel/submitting-a-patch.rst +++ b/docs/devel/submitting-a-patch.rst @@ -12,25 +12,18 @@ likely to be accepted and committed faster. This page seems very long, so if you are only trying to post a quick one-shot fix, the bare minimum we ask is that: -- You **must** provide a Signed-off-by: line (this is a hard - requirement because it's how you say "I'm legally okay to contribute - this and happy for it to go into QEMU", modeled after the `Linux kernel - `__ - policy.) ``git commit -s`` or ``git format-patch -s`` will add one. -- All contributions to QEMU must be **sent as patches** to the - qemu-devel `mailing list `__. - Patch contributions should not be posted on the bug tracker, posted on - forums, or externally hosted and linked to. (We have other mailing lists too, - but all patches must go to qemu-devel, possibly with a Cc: to another - list.) ``git send-email`` (`step-by-step setup - guide `__ and `hints and - tips `__) - works best for delivering the patch without mangling it, but - attachments can be used as a last resort on a first-time submission. -- You must read replies to your message, and be willing to act on them. - Note, however, that maintainers are often willing to manually fix up - first-time contributions, since there is a learning curve involved in - making an ideal patch submission. +.. list-table:: Minimal Checklist for Patches + :widths: 35 65 + :header-rows: 1 + + * - Check + - Reason + * - Patches contain Signed-off-by: Real Name + - States you are legally able to contribute the code. See :ref:`patch_emails_must_include_a_signed_off_by_line` + * - Sent as patch emails to ``qemu-devel@nongnu.org`` + - The project uses an email list based workflow. See :ref:`submitting_your_patches` + * - Be prepared to respond to review comments + - Code that doesn't pass review will not get merged. See :ref:`participating_in_code_review` You do not have to subscribe to post (list policy is to reply-to-all to preserve CCs and keep non-subscribers in the loop on the threads they @@ -229,6 +222,19 @@ bisection doesn't land on a known-broken state. Submitting your Patches ----------------------- +The QEMU project uses a public email based workflow for reviewing and +merging patches. As a result all contributions to QEMU must be **sent +as patches** to the qemu-devel `mailing list +`__. Patch +contributions should not be posted on the bug tracker, posted on +forums, or externally hosted and linked to. (We have other mailing +lists too, but all patches must go to qemu-devel, possibly with a Cc: +to another list.) ``git send-email`` (`step-by-step setup guide +`__ and `hints and tips +`__) +works best for delivering the patch without mangling it, but +attachments can be used as a last resort on a first-time submission. + .. _if_you_cannot_send_patch_emails: If you cannot send patch emails @@ -314,10 +320,12 @@ git repository to fetch the original commit. Patch emails must include a ``Signed-off-by:`` line ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -For more information see `SubmittingPatches 1.12 -`__. -This is vital or we will not be able to apply your patch! Please use -your real name to sign a patch (not an alias or acronym). +Your patches **must** include a Signed-off-by: line. This is a hard +requirement because it's how you say "I'm legally okay to contribute +this and happy for it to go into QEMU". The process is modelled after +the `Linux kernel +`__ +policy. If you wrote the patch, make sure your "From:" and "Signed-off-by:" lines use the same spelling. It's okay if you subscribe or contribute to @@ -327,6 +335,11 @@ include a "From:" line in the body of the email (different from your envelope From:) that will give credit to the correct author; but again, that author's Signed-off-by: line is mandatory, with the same spelling. +There are various tooling options for automatically adding these tags +include using ``git commit -s`` or ``git format-patch -s``. For more +information see `SubmittingPatches 1.12 +`__. + .. _include_a_meaningful_cover_letter: Include a meaningful cover letter @@ -397,9 +410,19 @@ Participating in Code Review ---------------------------- All patches submitted to the QEMU project go through a code review -process before they are accepted. Some areas of code that are well -maintained may review patches quickly, lesser-loved areas of code may -have a longer delay. +process before they are accepted. This will often mean a series will +go through a number of iterations before being picked up by +:ref:`maintainers`. You therefore should be prepared to +read replies to your messages and be willing to act on them. + +Maintainers are often willing to manually fix up first-time +contributions, since there is a learning curve involved in making an +ideal patch submission. However for the best results you should +proactively respond to suggestions with changes or justifications for +your current approach. + +Some areas of code that are well maintained may review patches +quickly, lesser-loved areas of code may have a longer delay. .. _stay_around_to_fix_problems_raised_in_code_review: