From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Wilfred Hughes Newsgroups: gmane.lisp.guile.devel Subject: Re: Status of elisp support in Guile Date: Fri, 14 Oct 2016 22:36:44 -0400 Message-ID: References: <87mvibdbfu.fsf@dustycloud.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a114cb210e241d4053ede3722 X-Trace: blaine.gmane.org 1476499070 3341 195.159.176.226 (15 Oct 2016 02:37:50 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 15 Oct 2016 02:37:50 +0000 (UTC) Cc: guile-devel To: Christopher Allan Webber Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sat Oct 15 04:37:46 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 1bvEqn-0006Rc-Hr for guile-devel@m.gmane.org; Sat, 15 Oct 2016 04:37:29 +0200 Original-Received: from localhost ([::1]:50197 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bvEql-0006Jq-Vq for guile-devel@m.gmane.org; Fri, 14 Oct 2016 22:37:28 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34917) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bvEqU-0006Jj-TD for guile-devel@gnu.org; Fri, 14 Oct 2016 22:37:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bvEqQ-00078m-AR for guile-devel@gnu.org; Fri, 14 Oct 2016 22:37:10 -0400 Original-Received: from mail-qk0-x22f.google.com ([2607:f8b0:400d:c09::22f]:35837) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1bvEqQ-00078d-2j for guile-devel@gnu.org; Fri, 14 Oct 2016 22:37:06 -0400 Original-Received: by mail-qk0-x22f.google.com with SMTP id z190so171053708qkc.2 for ; Fri, 14 Oct 2016 19:37:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wilfred-me-uk.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=m8ZBlFYeVCV8MOpEWkMvTrGuMx01y/zr03PBG1eZ8q4=; b=pa5kRUML1E/7eh03kPeU1FYrrnF+ExT5iajrJODbXPfgvmIUXq/dR+KODTj4ym0htj tpDiBb9mYsefL2rjMIn5puIzwD6tnt+ocxa+U8yB5epckkn1wsJxgC3PNK32c+NR5Lht QXRghXB+YK5/JmG6P4js/PmEeJjZ9xvupPr/PYhpoS2yaP8FxyZ/Emz9cJzF7VwQarEx k/6ZuuBe7y4OYIz6kpe2+s3jyHhDJm8sxPjnN/svG3Ne3EraDDvw+ypSEZGVhZZOvlC/ bb/4rPTw5h7V71BS+wA/1q0+OKwTJo55SMmp1bZ2weCMCn/pnDMYM9stZ1ASaNwtup9u 7acg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=m8ZBlFYeVCV8MOpEWkMvTrGuMx01y/zr03PBG1eZ8q4=; b=E1LPGVMsw8c05/VGXsO8+vAvnWx20QvdwTqyYcuOMC0G3GU7VKuDwTFU13r3e5ebPJ 533Ab2dYCOPiMeqlqOWXifeBsocALdc/WPyNCRMIsytFcyJwoLqOEvfl/6QiUkL69g4G GHB53ckQb3iJkudG22d8g8oBDqutsssp12at0z/gq6VVLT4XhbI97YhBKIoHWWh628SP gcccAgsJFQW2P6tBifkSgxht5rI2oNmzwOOtCZGU04dnYFpBzbCSTOsYwWbT4ImYgPra JJftZHomlTL932i+zjtEzWnf+A19ypoBovFGZcU1zFgkjXKHo+bXwMjJhK1xTfd/b8aB UWzg== X-Gm-Message-State: AA6/9Rl4HhEPmnMr0U1dQpeodZrBCzkU6vkpiO6w4c4daWeY99vkNUhE4ZyzBabf6TfAld9MczWpCA4+ybTsZg== X-Received: by 10.55.91.198 with SMTP id p189mr16733196qkb.132.1476499024784; Fri, 14 Oct 2016 19:37:04 -0700 (PDT) Original-Received: by 10.237.36.25 with HTTP; Fri, 14 Oct 2016 19:36:44 -0700 (PDT) X-Originating-IP: [146.115.86.181] In-Reply-To: <87mvibdbfu.fsf@dustycloud.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400d:c09::22f 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:18721 Archived-At: --001a114cb210e241d4053ede3722 Content-Type: text/plain; charset=UTF-8 > the branch added some non-trivial changes to the compiler, and I think Wingo wanted to review those before merging. That makes sense, thanks. I was hoping we could land the uncontroversial patches, to make the diff easier to review and simplify any future rebases. I mentioned the defsubst commits as they seemed reasonable at first glance. Is this feasible? > you'd definitely need to do copyright assignment for Guile. I think other "establishing yourself in the community" things apply, informally(??) I have copyright assignment all in order now :). I don't have any wild ambitions for sweeping changes, I just thought it might be easier to land simple docs patches without making work for the core Guile folks. On 10 October 2016 at 19:35, Christopher Allan Webber < cwebber@dustycloud.org> wrote: > 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(??) > --001a114cb210e241d4053ede3722 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
> the branch added some non-trivial changes t= o the compiler, and I think Wingo wanted to review
those before merging.=

That makes sense, thanks. I was hoping we could land the unco= ntroversial patches, to make the diff easier to review and simplify any fut= ure rebases. I mentioned the defsubst commits as they seemed reasonable at = first glance.

Is this feasible?

> yo= u'd definitely need to do copyright assignment for Guile.=C2=A0 I think= other "establishing
yourself in the community" things apply, informally(??)

I= have copyright assignment all in order now :). I don't have any wild a= mbitions for sweeping changes, I just thought it might be easier to land si= mple docs patches without making work for the core Guile folks.

On 10 October 2016 = at 19:35, Christopher Allan Webber <cwebber@dustycloud.org> wrote:
Wilfred Hugh= es 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!=C2=A0 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<= br> non-trivial changes to the compiler, and I think Wingo wanted to review
those before merging.=C2=A0 (I'm not really qualified to help, there.)<= br>
> Relatedly, what's the process for getting commit access to Guile?<= br>
I leave this one to someone else to reply to, but you'd definite= ly need
to do copyright assignment for Guile.=C2=A0 I think other "establishin= g
yourself in the community" things apply, informally(??)

--001a114cb210e241d4053ede3722--