From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs contributions, C and Lisp Date: Thu, 27 Mar 2014 18:39:18 +0200 Message-ID: <83siq3y4sp.fsf@gnu.org> References: <52FCD2B4.5080006@yandex.ru> <52FD9F1D.50205@yandex.ru> <83mwhucg1h.fsf@gnu.org> <878ute589i.fsf@fencepost.gnu.org> <83d2iqc84m.fsf@gnu.org> <87wqgxkcr9.fsf@yandex.ru> <834n41db0d.fsf@gnu.org> <52FE2985.4070703@yandex.ru> <831tz5daes.fsf@gnu.org> <8738jlohd6.fsf@yandex.ru> <83txc1bl83.fsf@gnu.org> <5300189A.9090208@yandex.ru> <83wqgv9fbj.fsf@gnu.org> <20140216180712.236069f6@forcix.jorgenschaefer.de> <83sirj9cyp.fsf@gnu.org> <20140217203145.71a849f7@forcix.jorgenschaefer.de> <837g8t8ouc.fsf@gnu.org> <87siq4aqq5.fsf@newcastle.ac.uk> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1395938370 15292 80.91.229.3 (27 Mar 2014 16:39:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 27 Mar 2014 16:39:30 +0000 (UTC) Cc: emacs-devel@gnu.org, forcer@forcix.cx, mina86@mina86.com, dgutov@yandex.ru To: phillip.lord@newcastle.ac.uk (Phillip Lord) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 27 17:39:39 2014 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 1WTDL6-0005wo-32 for ged-emacs-devel@m.gmane.org; Thu, 27 Mar 2014 17:39:36 +0100 Original-Received: from localhost ([::1]:54888 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WTDL5-0007Ew-F9 for ged-emacs-devel@m.gmane.org; Thu, 27 Mar 2014 12:39:35 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52846) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WTDKy-0007Ec-Be for emacs-devel@gnu.org; Thu, 27 Mar 2014 12:39:32 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WTDKq-00036V-Sg for emacs-devel@gnu.org; Thu, 27 Mar 2014 12:39:28 -0400 Original-Received: from mtaout23.012.net.il ([80.179.55.175]:59703) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WTDKq-00036E-Jw for emacs-devel@gnu.org; Thu, 27 Mar 2014 12:39:20 -0400 Original-Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0N3300700SW55S00@a-mtaout23.012.net.il> for emacs-devel@gnu.org; Thu, 27 Mar 2014 18:39:19 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N33007F4SXI2L60@a-mtaout23.012.net.il>; Thu, 27 Mar 2014 18:39:19 +0200 (IST) In-reply-to: <87siq4aqq5.fsf@newcastle.ac.uk> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.175 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:171036 Archived-At: > From: phillip.lord@newcastle.ac.uk (Phillip Lord) > Cc: Eli Zaretskii , , , > Jorgen Schaefer > Date: Thu, 27 Mar 2014 10:19:30 +0000 > > > What I found a bit discouraging is lack of responses to my patches. Admittedly, > > after re-reading etc/CONTRIBUTE I discovered I was sending them to the wrong > > place (emacs-devel instead of bug-gnu-emacs) but still it would be nice if > > someone yelled at me for using the wrong mailing list. > > Something like the gitorious merge request facilities would help here. > Then you would be able to see that your request had gone in. Mailing > lists are good for some things but maintaining a database is probably > not one of them. What we really need is to have in place an efficient and effective procedures for patch review and application. Without that, patches will collect dust on gitorious as they will in the archives of this or another mailing list. So I think you are putting the carriage ahead of the horse. We need first to have "patch pilots" and maybe some support rules, and then those people will pick up the tools they like best for doing their job. Having a database of patches that no one looks upon will lead us nowhere.