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 18:08:09 +0300 Message-ID: <83366z3sx2.fsf@gnu.org> References: <87368wrvf5.fsf@yahoo.com> <86k126d83n.wl-me@enzu.ru> <83pnbyckvv.fsf@gnu.org> <4923d7e98f5ed816a7569093dbc673153adcea88.camel@yandex.ru> <837dwb3zb6.fsf@gnu.org> <20200613141653.GA55972@breton.holly.idiocy.org> <835zbv3v6q.fsf@gnu.org> <20200613142329.GA56313@breton.holly.idiocy.org> <834krf3uij.fsf@gnu.org> <20200613150230.GA56583@breton.holly.idiocy.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="88376"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, stefan@marxist.se, hi-angel@yandex.ru To: Alan Third Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 13 17:08:59 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 1jk7mE-000MqI-Hm for ged-emacs-devel@m.gmane-mx.org; Sat, 13 Jun 2020 17:08:58 +0200 Original-Received: from localhost ([::1]:52814 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jk7mD-0002Gg-J9 for ged-emacs-devel@m.gmane-mx.org; Sat, 13 Jun 2020 11:08:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45090) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jk7lc-0001ev-Tr for emacs-devel@gnu.org; Sat, 13 Jun 2020 11:08:20 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:58359) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jk7lc-0007qt-5A; Sat, 13 Jun 2020 11:08:20 -0400 Original-Received: from [176.228.60.248] (port=4144 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jk7la-0003pk-8A; Sat, 13 Jun 2020 11:08:18 -0400 In-Reply-To: <20200613150230.GA56583@breton.holly.idiocy.org> (message from Alan Third on Sat, 13 Jun 2020 17:02:33 +0200 (CEST)) 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:252174 Archived-At: > Date: Sat, 13 Jun 2020 17:02:33 +0200 (CEST) > From: Alan Third > Cc: hi-angel@yandex.ru, stefan@marxist.se, emacs-devel@gnu.org > > No, I didn't intend to attack you, I was just curious because I would > have thought it should be easy for Emacs to take the email > (git-format-patch format is a plain email, as is the mbox format) and > pipe it straight into git am. Of course, that's what I usually do. But when the email has only a patch, not a result of git-format-patch, I don't want to try, because some irregularity of the format could fail the patch and/or the following commit, and I would then need to recover, fix the patch or apply it manually, etc. So I use "git apply" in those cases instead. Which needs a separate commit step, including specifying the right author and date. And the commit log message needs a manual fix in any case.