From: Wilfred Hughes <me@wilfred.me.uk>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Status of elisp support in Guile
Date: Fri, 14 Oct 2016 22:36:44 -0400 [thread overview]
Message-ID: <CAFXAjY5gxoj1WLuXDeDE7aRA0fVoW7bM2ZMe99wFoRRSmEpAEg@mail.gmail.com> (raw)
In-Reply-To: <87mvibdbfu.fsf@dustycloud.org>
[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]
> 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(??)
>
[-- Attachment #2: Type: text/html, Size: 2631 bytes --]
next prev parent reply other threads:[~2016-10-15 2:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 2:42 Status of elisp support in Guile Wilfred Hughes
2016-10-10 23:35 ` Christopher Allan Webber
2016-10-15 2:36 ` Wilfred Hughes [this message]
2016-10-17 14:53 ` Christopher Allan Webber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFXAjY5gxoj1WLuXDeDE7aRA0fVoW7bM2ZMe99wFoRRSmEpAEg@mail.gmail.com \
--to=me@wilfred.me.uk \
--cc=cwebber@dustycloud.org \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).