From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Why are so many great packages not trying to get included in GNU Emacs? WAS: Re: Making Emacs more friendly to newcomers Date: Sat, 13 Jun 2020 22:33:21 +0300 Message-ID: <83o8pm3gn2.fsf@gnu.org> References: <87mu78huhx.fsf_-_@yahoo.com> <87k12bdgx7.fsf@yahoo.com> <87r1wi7a8o.fsf@yahoo.com> <875zdteybt.fsf@runbox.com> <87368wrvf5.fsf@yahoo.com> <86k126d83n.wl-me@enzu.ru> <83pnbyckvv.fsf@gnu.org> <4923d7e98f5ed816a7569093dbc673153adcea88.camel@yandex.ru> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="528"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, stefan@marxist.se, dgutov@yandex.ru To: Konstantin Kharlamov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 13 21:34:25 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jkBv5-000Xzr-VA for ged-emacs-devel@m.gmane-mx.org; Sat, 13 Jun 2020 21:34:23 +0200 Original-Received: from localhost ([::1]:53152 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jkBv4-0001Ma-Jp for ged-emacs-devel@m.gmane-mx.org; Sat, 13 Jun 2020 15:34:22 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33416) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jkBua-0000uj-KN for emacs-devel@gnu.org; Sat, 13 Jun 2020 15:33:52 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:34124) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jkBuZ-0005kP-RB; Sat, 13 Jun 2020 15:33:51 -0400 Original-Received: from [176.228.60.248] (port=4790 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jkBuX-0006XE-5x; Sat, 13 Jun 2020 15:33:51 -0400 In-Reply-To: (message from Konstantin Kharlamov on Sat, 13 Jun 2020 22:23:30 +0300) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:252202 Archived-At: > From: Konstantin Kharlamov > Date: Sat, 13 Jun 2020 22:23:30 +0300 > > having a list of function names with description for each does not > make one. Instead it should be an overview of what is done, why, and how. It should be both, actually. > Suppose you have a patch that deduplicates the same code pattern across 34 > functions by factoring it out to a single short function. Do you really need > that list? No, and no one will ever ask you to describe such mechanistic changes one by one. It's all in the GNU Coding Standards, btw. I suggest to read that.