From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KLTfU-0007NO-7t for qemu-devel@nongnu.org; Tue, 22 Jul 2008 22:01:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KLTfS-0007Lx-OW for qemu-devel@nongnu.org; Tue, 22 Jul 2008 22:01:27 -0400 Received: from [199.232.76.173] (port=52815 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KLTfS-0007Lg-FI for qemu-devel@nongnu.org; Tue, 22 Jul 2008 22:01:26 -0400 Received: from an-out-0708.google.com ([209.85.132.251]:56545) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KLTfR-0004AR-WC for qemu-devel@nongnu.org; Tue, 22 Jul 2008 22:01:26 -0400 Received: by an-out-0708.google.com with SMTP id d18so852461and.130 for ; Tue, 22 Jul 2008 19:01:25 -0700 (PDT) Message-ID: <488690D7.6060104@codemonkey.ws> Date: Tue, 22 Jul 2008 21:00:55 -0500 From: Anthony Liguori MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Proposal: Using DCO for QEMU Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "qemu-devel@nongnu.org" Many projects (most notably, the Linux kernel) use the DCO process to track patch origins[1]. This involves adding a "Signed-off-by:" tag to any patch you submit. A maintainer will then add their own Signed-off-by tag before committing. This helps keep track of where patches come from and who has handled them. It's pretty handy when tracking down changes. I think it would be a good idea for QEMU to use this process. Some people already are using this process so it shouldn't be that much of an adjustment. [1] http://ltp.sourceforge.net/DCO.txt Regards, Anthony Liguori