From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Seeking a "Patch Champion" Date: Sun, 24 Apr 2016 00:45:41 +0300 Message-ID: <30093698-1694-5755-c1d2-22517191ac3f@yandex.ru> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1461447968 756 80.91.229.3 (23 Apr 2016 21:46:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 23 Apr 2016 21:46:08 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Apr 23 23:46:03 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1au5NK-0000fU-I4 for ged-emacs-devel@m.gmane.org; Sat, 23 Apr 2016 23:46:02 +0200 Original-Received: from localhost ([::1]:53569 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1au5NJ-0004uv-O6 for ged-emacs-devel@m.gmane.org; Sat, 23 Apr 2016 17:46:01 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48652) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1au5N5-0004rT-Fi for emacs-devel@gnu.org; Sat, 23 Apr 2016 17:45:48 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1au5N2-0003ob-9w for emacs-devel@gnu.org; Sat, 23 Apr 2016 17:45:47 -0400 Original-Received: from mail-wm0-x243.google.com ([2a00:1450:400c:c09::243]:34097) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1au5N2-0003oQ-28 for emacs-devel@gnu.org; Sat, 23 Apr 2016 17:45:44 -0400 Original-Received: by mail-wm0-x243.google.com with SMTP id n3so14416369wmn.1 for ; Sat, 23 Apr 2016 14:45:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=xAWtzS4JIG8s7dPiuzx8OnHTComDkKmZopOTY2kSCZo=; b=q1be+FBNDdwsrnW+Ct8mx4vU86JTDZLN4YOHeUz3LOHYico9ITRTMoJMasPu5OhX93 Tyvs5ARPw3RWbNEPtAJLxXZ1PoNcnStmi6NaPq51XCD+oimU2jvkcj3k6h88u+CV4bxA VfeL/h5aryteJ4IKdeEYXREBLRZnz++IAu+eW3dc3/l5KIEk9mALEpf9K/5Dz85hDA1X sBFYpSjkWqzBUTQoYYdf7MNb/U7stbdQFLcP000JiZBkibE1fqPRHyul0ZtNLRJmno2o 4mvsNYjySE8GGvTQ6UYsMvTBDLF1XnT/11djMBBoIFepLaGKQnwNeieERG2YLKHL8JeT bn0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=xAWtzS4JIG8s7dPiuzx8OnHTComDkKmZopOTY2kSCZo=; b=C75EBVenIEDTgPRS0N8heaOfJLLcWNHsDAZfulem/Wm7NmIktNIxvp8S/NyxrYRRUT yFX8fsNbYxIG6GF3SFpatJ8Tf2JQAsNLnzbeBUqi5YR97zyKIbD6pNOPQubwTHTpt0mR StA5IVmCYtPf9ZkW0tUVOI+9X7+xV6mZDQ7EceVXAXI8vRgr4jEd5ZNG8MBtsEu4Scy4 0ZY80n7loBaDPLEcV5RnrUf59CanKdfS439XPnLgGdkHkFUWRNjR0O1SkS+eR+WTaUnR X7+WHLk7S6mNkHOxwOI1zvFTQYa7v+Lud8XROuzjCMksIUJulg+MA803E+DlQsJstPP3 vYYA== X-Gm-Message-State: AOPr4FUAlf+pvGnj/RwzLCEqQqE5c1u3YzXueQ2So7JQNMyOsHTO6CuTZ0qWUCrNRBRDAA== X-Received: by 10.194.60.235 with SMTP id k11mr26592360wjr.148.1461447943282; Sat, 23 Apr 2016 14:45:43 -0700 (PDT) Original-Received: from [192.168.1.2] ([185.105.175.24]) by smtp.googlemail.com with ESMTPSA id kj9sm15081373wjb.14.2016.04.23.14.45.42 for (version=TLSv1/SSLv3 cipher=OTHER); Sat, 23 Apr 2016 14:45:42 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:400c:c09::243 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:203230 Archived-At: Hey John, On 04/24/2016 12:22 AM, John Wiegley wrote: > Largely this is because we have so many of them: 435 this year, so far. And no > one (besides myself, who has been fully derelict in this duty) is currently > dedicated to ensuring that each of these patches receives due attention. > Unless someone with commit access has a particular interest in attending to a > patch right away, it generally fades into history. > > I would like to change this state of affairs by asking for a core of > volunteers who are willing to champion patches, and ensure that they go > through a process of review before being either rejected or applied. > > To assist this effort, I've connected our mailing lists with a service running > on my own VPS (for now) called "Patchwork"[1]: > > http://patchwork.newartisans.com/ This is great. I will try it sometime. There's one problem in the current list: it doesn't seem to take into account the status of the related bugs. Here are a few entries from bugs that have already been closed: http://patchwork.newartisans.com/patch/538/ http://patchwork.newartisans.com/patch/565/ http://patchwork.newartisans.com/patch/553/ Shouldn't they have a different status, at least? > Every patch sent -- either on emacs-devel or bug-gnu-emacs -- is captured by > this server and assigned a ticket number. Note: these are not *issue tickets*, > but *patch tickets*, one for each patch, even if multiple patches are > submitted for a single bug[2]. Could they be grouped somehow? Most of the time, the next patch submitted to a bug report supersedes the previous one. Best regards, Dmitry.