From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:59055) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iwN0U-0000kn-TW for guix-patches@gnu.org; Tue, 28 Jan 2020 04:18:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iwN0T-0000tq-VY for guix-patches@gnu.org; Tue, 28 Jan 2020 04:18:02 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:53558) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iwN0T-0000th-Sf for guix-patches@gnu.org; Tue, 28 Jan 2020 04:18:01 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iwN0T-00088r-PD for guix-patches@gnu.org; Tue, 28 Jan 2020 04:18:01 -0500 Subject: bug#39320: [PATCH] gnu: Add emacs-mwim. Resent-To: guix-patches@gnu.org Resent-Message-ID: From: Nicolas Goaziou References: <20200127235036.14809-1-mab@gnu.org> <87pnf4m35y.fsf@nicolasgoaziou.fr> <87eevkhu0h.fsf@gnu.org> Date: Tue, 28 Jan 2020 10:17:31 +0100 In-Reply-To: <87eevkhu0h.fsf@gnu.org> (Amin Bandali's message of "Tue, 28 Jan 2020 03:20:30 -0500") Message-ID: <87zhe8djo4.fsf@nicolasgoaziou.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Amin Bandali Cc: 39320-done@debbugs.gnu.org Amin Bandali writes: > The main reason is that commit is a fix for a reported issue [0], but > sadly isn=E2=80=99t part of any tagged release. Further, the repository = hasn=E2=80=99t > seen any activity in over a year, so I figured the likelihood of the > author tagging a new release any time soon is pretty slim. > > [0]: https://github.com/alezost/mwim.el/issues/12 > > For what it=E2=80=99s worth, I=E2=80=99ve had this package definition in = my personal > Guix channel for about six months now, and no activity in the upstream > repo through this time. > > How does the following v2 look? Fine. I applied it as 19568f9e79ed74b7100d25d3f2ea245f857ca742. Thank you. Regards,