From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Wilfred Hughes <me@wilfred.me.uk>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Status of elisp support in Guile
Date: Mon, 17 Oct 2016 09:53:37 -0500 [thread overview]
Message-ID: <87eg3f9gcu.fsf@dustycloud.org> (raw)
In-Reply-To: <CAFXAjY5gxoj1WLuXDeDE7aRA0fVoW7bM2ZMe99wFoRRSmEpAEg@mail.gmail.com>
Wilfred Hughes writes:
>> 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.
Again, can't speak to giving out commit access... that's not my area.
But if you have documentation patches, and since you've done copyright
assignment, those would be most welcome. If you could post them to the
list, I could help get them into the wip-elisp branch!
prev parent reply other threads:[~2016-10-17 14:53 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
2016-10-17 14:53 ` Christopher Allan Webber [this message]
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=87eg3f9gcu.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guile-devel@gnu.org \
--cc=me@wilfred.me.uk \
/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).