From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55784) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cC40n-0007v5-EG for qemu-devel@nongnu.org; Wed, 30 Nov 2016 07:29:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cC40m-0003Zh-EL for qemu-devel@nongnu.org; Wed, 30 Nov 2016 07:29:21 -0500 Received: from mx1.redhat.com ([209.132.183.28]:57574) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cC40m-0003ZC-8s for qemu-devel@nongnu.org; Wed, 30 Nov 2016 07:29:20 -0500 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 502117F3F5 for ; Wed, 30 Nov 2016 12:29:19 +0000 (UTC) Message-ID: <1480508956.20354.28.camel@redhat.com> From: Gerd Hoffmann Date: Wed, 30 Nov 2016 13:29:16 +0100 In-Reply-To: <0a6692f7-d2d3-2902-d5f0-77035c90a6cb@redhat.com> References: <9151aa4b-44ed-ee0f-4dac-581931b3e899@redhat.com> <1480503358.20354.23.camel@redhat.com> <0a6692f7-d2d3-2902-d5f0-77035c90a6cb@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 Subject: Re: [Qemu-devel] a suggestion to place *.c hunks last in patches List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek Cc: qemu devel list Hi, > > Want sent a patch? >=20 > What file for? :) create something like scripts/git.orderfile, so people have just to run "git config diff.orderfile scripts/git.orderfile" to enable it, and we can refine the config without having everybody update the orderfile manually? > I've considered modifying > , but that article is > humongous already. >=20 > Nonetheless, section "Make code motion patches easy to review" mentions > some diff.* settings, so I guess a new section after it ("Format > declarative and abstract changes near the top") would be appropriate, if > there's no disagreement. Yep, adding to the wiki sounds good too. > > Can this be automatically enabled per repo, like .gitignore, so it work= s > > without everybody tweaking its local git config? >=20 > Not to my understanding. Too bad. cheers, Gerd