From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45247) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1etMJA-00018e-Or for qemu-devel@nongnu.org; Tue, 06 Mar 2018 18:47:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1etMJ7-0007KX-LS for qemu-devel@nongnu.org; Tue, 06 Mar 2018 18:47:48 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:51353) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1etMJ7-0007KH-EY for qemu-devel@nongnu.org; Tue, 06 Mar 2018 18:47:45 -0500 Date: Tue, 6 Mar 2018 18:47:42 -0500 From: "Emilio G. Cota" Message-ID: <20180306234742.GA26112@flamenco> References: <1520369037-37977-1-git-send-email-mjc@sifive.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v1 00/22] Spec conformance bug fixes and cleanups List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Clark Cc: QEMU Developers , Bastian Koppelmann , Palmer Dabbelt , Sagar Karandikar , RISC-V Patches On Wed, Mar 07, 2018 at 12:07:18 +1300, Michael Clark wrote: > BTW Apologies for the duplicate emails. I'm still getting to grips with the > git-sendemail workflow and was using a sed script to Add Cc's which munged > the headers as it didn't take into account Subject lines flowing to two > lines. I guess I can just include Cc: in the commit message? and > git-format-patch will handle it for me? or I just should how to use > git-publish... I don't have experience with git-publish. The following two suggestions might help though: - Yes, add Cc's to individual patches -- those are picked up by send-email. That also applies to the cover letter, although note that if you use --compose then Cc's won't be picked up. Instead, just write the cover letter into a 0000-$cover.patch (with Cc's in there) and do not use --compose. - Use send-email's --dry-run option to make sure everything looks good without actually sending any emails. > I still have to work on Igor's requested change to CPU initializer > declarations, and i'd also like to get the patch in that fixes fmin/fmax > test failures using the riscv-tests testsuite by implementing IEEE-754 > minimumNumber/maximumNumber. I'll try to get a patch onto the list before > soft-freeze. I dropped the patch which was in an earlier version of our > port patch series due to a conflict with changes in softfloat (conversion > of minmax from a macro to a static function iirc). Note that if you're fixing a bug (and the fmin/fmax patch qualifies), you can definitely get it merged post-soft-freeze. E.