From nobody Mon Apr 29 02:38:13 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zoho.com: domain of gnu.org designates 208.118.235.17 as permitted sender) client-ip=208.118.235.17; envelope-from=qemu-devel-bounces+importer=patchew.org@nongnu.org; helo=lists.gnu.org; Authentication-Results: mx.zohomail.com; spf=pass (zoho.com: domain of gnu.org designates 208.118.235.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; dmarc=fail(p=none dis=none) header.from=redhat.com Return-Path: Received: from lists.gnu.org (208.118.235.17 [208.118.235.17]) by mx.zohomail.com with SMTPS id 1517809765754942.1128639147325; Sun, 4 Feb 2018 21:49:25 -0800 (PST) Received: from localhost ([::1]:57758 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eiZeW-0001ge-1G for importer@patchew.org; Mon, 05 Feb 2018 00:49:16 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52449) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eiZd4-0000uk-HE for qemu-devel@nongnu.org; Mon, 05 Feb 2018 00:47:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eiZd2-0006pv-Oy for qemu-devel@nongnu.org; Mon, 05 Feb 2018 00:47:46 -0500 Received: from mx1.redhat.com ([209.132.183.28]:40352) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eiZd2-0006pk-Ig for qemu-devel@nongnu.org; Mon, 05 Feb 2018 00:47:44 -0500 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id AEC4437E6E; Mon, 5 Feb 2018 05:47:43 +0000 (UTC) Received: from lemon.usersys.redhat.com (ovpn-12-58.pek2.redhat.com [10.72.12.58]) by smtp.corp.redhat.com (Postfix) with ESMTP id 1AA535D9CB; Mon, 5 Feb 2018 05:47:41 +0000 (UTC) From: Fam Zheng To: qemu-devel@nongnu.org Date: Mon, 5 Feb 2018 13:47:24 +0800 Message-Id: <20180205054725.25634-2-famz@redhat.com> In-Reply-To: <20180205054725.25634-1-famz@redhat.com> References: <20180205054725.25634-1-famz@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Mon, 05 Feb 2018 05:47:43 +0000 (UTC) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.132.183.28 Subject: [Qemu-devel] [PATCH v3 1/2] Add a git-publish configuration file X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: marcandre.lureau@gmail.com, mdroth@linux.vnet.ibm.com, stefanha@redhat.com Errors-To: qemu-devel-bounces+importer=patchew.org@nongnu.org Sender: "Qemu-devel" X-ZohoMail: RSF_0 Z_629925259 SPT_0 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" git-publish [1] is a convenient tool to send patches and has been popular among QEMU developers. Recently it has been made available in Fedora official repo thanks to Stefan's work. One nice feature of the tool is a per-project configuration with profiles, especially in which the cccmd option is a handy method to create the Cc list. [1]: https://github.com/stefanha/git-publish Signed-off-by: Fam Zheng Reviewed-by: Marc-Andr=C3=A9 Lureau --- .gitpublish | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 58 insertions(+) create mode 100644 .gitpublish diff --git a/.gitpublish b/.gitpublish new file mode 100644 index 0000000000..ed48f6e52c --- /dev/null +++ b/.gitpublish @@ -0,0 +1,58 @@ +# +# Common git-publish profiles that can be used to send patches to QEMU ups= tream. +# +# See https://github.com/stefanha/git-publish for more information +# +[gitpublishprofile "default"] +base =3D master +prefix =3D PATCH +to =3D qemu-devel@nongnu.org +cccmd =3D scripts/get_maintainer.pl --noroles --norolestats --nogit --nogi= t-fallback 2>/dev/null + +[gitpublishprofile "rfc"] +base =3D master +prefix =3D RFC PATCH +to =3D qemu-devel@nongnu.org +cccmd =3D scripts/get_maintainer.pl --noroles --norolestats --nogit --nogi= t-fallback 2>/dev/null + +[gitpublishprofile "stable"] +base =3D master +prefix =3D PATCH +to =3D qemu-devel@nongnu.org +cc =3D qemu-stable@nongnu.org +cccmd =3D scripts/get_maintainer.pl --noroles --norolestats --nogit --nogi= t-fallback 2>/dev/null + +[gitpublishprofile "trivial"] +base =3D master +prefix =3D PATCH +to =3D qemu-devel@nongnu.org +cc =3D qemu-trivial@nongnu.org +cccmd =3D scripts/get_maintainer.pl --noroles --norolestats --nogit --nogi= t-fallback 2>/dev/null + +[gitpublishprofile "block"] +base =3D master +prefix =3D PATCH +to =3D qemu-devel@nongnu.org +cc =3D qemu-block@nongnu.org +cccmd =3D scripts/get_maintainer.pl --noroles --norolestats --nogit --nogi= t-fallback 2>/dev/null + +[gitpublishprofile "arm"] +base =3D master +prefix =3D PATCH +to =3D qemu-devel@nongnu.org +cc =3D qemu-arm@nongnu.org +cccmd =3D scripts/get_maintainer.pl --noroles --norolestats --nogit --nogi= t-fallback 2>/dev/null + +[gitpublishprofile "s390"] +base =3D master +prefix =3D PATCH +to =3D qemu-devel@nongnu.org +cc =3D qemu-s390@nongnu.org +cccmd =3D scripts/get_maintainer.pl --noroles --norolestats --nogit --nogi= t-fallback 2>/dev/null + +[gitpublishprofile "ppc"] +base =3D master +prefix =3D PATCH +to =3D qemu-devel@nongnu.org +cc =3D qemu-ppc@nongnu.org +cccmd =3D scripts/get_maintainer.pl --noroles --norolestats --nogit --nogi= t-fallback 2>/dev/null --=20 2.14.3 From nobody Mon Apr 29 02:38:13 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zoho.com: domain of gnu.org designates 208.118.235.17 as permitted sender) client-ip=208.118.235.17; envelope-from=qemu-devel-bounces+importer=patchew.org@nongnu.org; helo=lists.gnu.org; Authentication-Results: mx.zohomail.com; spf=pass (zoho.com: domain of gnu.org designates 208.118.235.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; dmarc=fail(p=none dis=none) header.from=redhat.com Return-Path: Received: from lists.gnu.org (lists.gnu.org [208.118.235.17]) by mx.zohomail.com with SMTPS id 1517809859294669.7323638871529; Sun, 4 Feb 2018 21:50:59 -0800 (PST) Received: from localhost ([::1]:57835 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eiZg8-0002z9-L6 for importer@patchew.org; Mon, 05 Feb 2018 00:50:56 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52466) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eiZd5-0000vD-OZ for qemu-devel@nongnu.org; Mon, 05 Feb 2018 00:47:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eiZd4-0006qV-MM for qemu-devel@nongnu.org; Mon, 05 Feb 2018 00:47:47 -0500 Received: from mx1.redhat.com ([209.132.183.28]:51862) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eiZd4-0006qE-G1 for qemu-devel@nongnu.org; Mon, 05 Feb 2018 00:47:46 -0500 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id B34425D685; Mon, 5 Feb 2018 05:47:45 +0000 (UTC) Received: from lemon.usersys.redhat.com (ovpn-12-58.pek2.redhat.com [10.72.12.58]) by smtp.corp.redhat.com (Postfix) with ESMTP id 32E745D9CB; Mon, 5 Feb 2018 05:47:43 +0000 (UTC) From: Fam Zheng To: qemu-devel@nongnu.org Date: Mon, 5 Feb 2018 13:47:25 +0800 Message-Id: <20180205054725.25634-3-famz@redhat.com> In-Reply-To: <20180205054725.25634-1-famz@redhat.com> References: <20180205054725.25634-1-famz@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Mon, 05 Feb 2018 05:47:45 +0000 (UTC) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.132.183.28 Subject: [Qemu-devel] [PATCH v3 2/2] README: Document 'git-publish' workflow X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: marcandre.lureau@gmail.com, mdroth@linux.vnet.ibm.com, stefanha@redhat.com Errors-To: qemu-devel-bounces+importer=patchew.org@nongnu.org Sender: "Qemu-devel" X-ZohoMail: RSF_0 Z_629925259 SPT_0 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Signed-off-by: Fam Zheng Reviewed-by: Marc-Andr=C3=A9 Lureau --- README | 30 +++++++++++++++++++++++++++++- 1 file changed, 29 insertions(+), 1 deletion(-) diff --git a/README b/README index b92a07a61a..d1a944ce20 100644 --- a/README +++ b/README @@ -56,7 +56,7 @@ The QEMU source code is maintained under the GIT version = control system. =20 git clone git://git.qemu.org/qemu.git =20 -When submitting patches, the preferred approach is to use 'git +When submitting patches, one common approach is to use 'git format-patch' and/or 'git send-email' to format & send the mail to the qemu-devel@nongnu.org mailing list. All patches submitted must contain a 'Signed-off-by' line from the author. Patches should follow the @@ -68,6 +68,34 @@ the QEMU website https://qemu.org/Contribute/SubmitAPatch https://qemu.org/Contribute/TrivialPatches =20 +A 'git-profile' utility was created to make above process less +cumbersome, and is highly recommended for making regular contributions, +or even just for sending consecutive patch series revisions. It also +requires a working 'git send-email' setup, and by default doesn't +automate everything, so you may want to go through the above steps +manually for once. + +For installation instructions, please go to + + https://github.com/stefanha/git-publish + +The workflow with 'git-publish' is: + + $ git checkout master -b my-feature + $ # work on new commits, add your 'Signed-off-by' lines to each + $ git publish + +Your patch series will be sent and tagged as my-feature-v1 if you need to = refer +back to it in the future. + +Sending v2: + + $ git checkout my-feature # same topic branch + $ # making changes to the commits (using 'git rebase', for example) + $ git publish + +Your patch series will be sent with 'v2' tag in the subject and the git tip +will be tagged as my-feature-v2. =20 Bug reporting =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --=20 2.14.3