From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47229) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WNLhN-0006zJ-FX for qemu-devel@nongnu.org; Tue, 11 Mar 2014 08:22:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WNLhH-0002zb-Gu for qemu-devel@nongnu.org; Tue, 11 Mar 2014 08:22:21 -0400 Received: from mx1.redhat.com ([209.132.183.28]:60869) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WNLhH-0002zG-8z for qemu-devel@nongnu.org; Tue, 11 Mar 2014 08:22:15 -0400 Date: Tue, 11 Mar 2014 14:22:07 +0200 From: "Michael S. Tsirkin" Message-ID: <20140311122207.GA30782@redhat.com> References: <1394392713-31471-1-git-send-email-mst@redhat.com> <20140310190515.GA16291@redhat.com> <20140311112242.GA17666@redhat.com> <20140311114915.GA30708@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PULL v3 00/14] acpi, pc, pci, virtio, memory bug fixes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: QEMU Developers , Anthony Liguori On Tue, Mar 11, 2014 at 12:09:40PM +0000, Peter Maydell wrote: > On 11 March 2014 11:49, Michael S. Tsirkin wrote: > > On Tue, Mar 11, 2014 at 11:32:41AM +0000, Peter Maydell wrote: > >> That won't help with removing the warning. What gpg > >> is saying here is "I found this key in the keyring, > >> and the signature checks out, but there's no chain > >> of trust between the person who applied the pull > >> and that key". That is, I haven't signed your key. > > > > Okay ... would you like to sign it? > > Didn't you go to the key signing party at the forum? > > If yes you have all the data :) > > At the forum I only signed keys where the other > person had been sufficiently organised to get their > key onto the pre-printed list Anthony sent out and > were clearly following the instructions. (Basically > I wasn't expecting to be applying other peoples' > pull requests at that time so it seemed sufficient > to do a mutual signing with a reasonable number of > developers.) I can't remember why I put a cross next to > your name at this point, but obviously I can't sign > your key now if I didn't choose to do so then; that > would be breaking the whole point of doing in person > checks. I was on the list so not sure why, oh well. But a chain of trust can still be established. A bunch of people signed my key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0xC3503912AFBE8E67 maybe you trust some of these keys? > > But the commit log will include the warning forever I think? > > True, but does that matter? > > thanks > -- PMM I'm just saying that it's not nice to ignore warnings as a general policy. If they are benign I think it's better to find a way to suppress them. -- MST