From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MtM1a-0006vD-Db for qemu-devel@nongnu.org; Thu, 01 Oct 2009 09:48:50 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MtM1W-0006uK-2l for qemu-devel@nongnu.org; Thu, 01 Oct 2009 09:48:50 -0400 Received: from [199.232.76.173] (port=58302 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MtM1V-0006uH-UR for qemu-devel@nongnu.org; Thu, 01 Oct 2009 09:48:45 -0400 Received: from mail-px0-f179.google.com ([209.85.216.179]:51389) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MtM1V-0004Ga-NJ for qemu-devel@nongnu.org; Thu, 01 Oct 2009 09:48:45 -0400 Received: by pxi9 with SMTP id 9so155013pxi.4 for ; Thu, 01 Oct 2009 06:48:44 -0700 (PDT) Message-ID: <4AC4B336.6090301@codemonkey.ws> Date: Thu, 01 Oct 2009 08:48:38 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 1/6] char: Emit 'OPENED' events on char device open References: <1254225888-17093-1-git-send-email-amit.shah@redhat.com> <1254225888-17093-2-git-send-email-amit.shah@redhat.com> <4AC3C9FD.3050705@codemonkey.ws> <20091001045622.GB18563@amit-x200.redhat.com> <4AC4A676.4050702@codemonkey.ws> <4AC4B1F1.7070103@redhat.com> In-Reply-To: <4AC4B1F1.7070103@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: Amit Shah , qemu-devel@nongnu.org Gerd Hoffmann wrote: > On 10/01/09 14:54, Anthony Liguori wrote: >>>> You should always build without an explicit --target-list to avoid >>>> this in the future. >>> >>> Sure -- I intend to when I send a request for the merging once all the >>> comments have been sorted out. >> >> If you don't intend a patch series to be merged, then you should put >> [RFC] in the subject. > > Huh? I'm a bit surprised you are considering patches for merge which > are discussed alot on the list and thus most likely not final. Amit has repeatedly asked me to consider these series for merging. If there is no indicator in the subject that they are not intended to be merged, then they're going to go through staging. I'll remove them from staging once I see that the patches are contended. The reason I do this is to make sure that patches don't get dropped. There's no excuse for a patch to be on the mailing list that isn't properly tested (especially build tested) without an appropriate tag indicating that like [RFC]. Regards, Anthony Liguori > cheers, > Gerd