From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Christopher Allan Webber Newsgroups: gmane.lisp.guile.devel Subject: Re: Status of elisp support in Guile Date: Mon, 10 Oct 2016 18:35:49 -0500 Message-ID: <87mvibdbfu.fsf@dustycloud.org> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1476142594 10644 195.159.176.226 (10 Oct 2016 23:36:34 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 10 Oct 2016 23:36:34 +0000 (UTC) User-Agent: mu4e 0.9.16; emacs 25.1.1 Cc: guile-devel To: Wilfred Hughes Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Tue Oct 11 01:36:30 2016 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1btk7K-000192-K3 for guile-devel@m.gmane.org; Tue, 11 Oct 2016 01:36:22 +0200 Original-Received: from localhost ([::1]:53034 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1btk7I-0006Du-6U for guile-devel@m.gmane.org; Mon, 10 Oct 2016 19:36:20 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49514) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1btk73-0006Dd-A1 for guile-devel@gnu.org; Mon, 10 Oct 2016 19:36:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1btk70-0001uR-5s for guile-devel@gnu.org; Mon, 10 Oct 2016 19:36:05 -0400 Original-Received: from dustycloud.org ([50.116.34.160]:40508) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1btk70-0001rQ-14 for guile-devel@gnu.org; Mon, 10 Oct 2016 19:36:02 -0400 Original-Received: from oolong (localhost [127.0.0.1]) by dustycloud.org (Postfix) with ESMTPS id D950F2670C; Mon, 10 Oct 2016 19:35:49 -0400 (EDT) In-reply-to: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 50.116.34.160 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: "guile-devel" Xref: news.gmane.org gmane.lisp.guile.devel:18710 Archived-At: Wilfred Hughes writes: > I've noticed that NEWS in Guile trunk says: > > ** Complete Emacs-compatible Elisp implementation > > However, I can see that there are 36 commits on the wip-elisp branch > that aren't in master. For example, defsubst support[1] seems only to > be on wip-elisp branch. It's still the case the guile-emacs docs[2] > recommend using the wip-elisp branch. > > I can merge master into wip-elisp only one trivial conflict[3]. Can > anyone shed any light on the work outstanding here, and the process to > land these patches? Hi! So, I'm the one who did the most recent rebase of wip-elisp. Last I heard, Wingo was interested in merging, but looked over the branch and saw that it wasn't a trivial merge... the branch added some non-trivial changes to the compiler, and I think Wingo wanted to review those before merging. (I'm not really qualified to help, there.) > Relatedly, what's the process for getting commit access to Guile? I leave this one to someone else to reply to, but you'd definitely need to do copyright assignment for Guile. I think other "establishing yourself in the community" things apply, informally(??)