From: Colin Woodbury <colin@fosskers.ca>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org, "Linus Björnstam" <linus.bjornstam@veryfast.biz>
Subject: Re: [PATCHv3] Extensions for SRFI-171 (Transducers)
Date: Thu, 18 May 2023 09:36:58 +0900 [thread overview]
Message-ID: <07c2b0bb-6c22-da79-2776-362f36ebd19d@fosskers.ca> (raw)
In-Reply-To: <87ilgwwbao.fsf@gnu.org>
Hi! Forgive the delay; my copyright assignment for Guile has finally
gone through. Please let me know if the patches are still good!
Colin
On 1/24/23 18:07, Ludovic Courtès wrote:
> Hi Colin,
>
> Colin Woodbury <colin@fosskers.ca> skribis:
>
>> Sorry if I wasn't clear - I have alright assigned copyright to the FSF
>> (about 1.5 years ago). Things should be good to go, unless I've
>> misunderstood.
> I checked the records on fencepost.gnu.org and AFAICS, you assigned
> copyright for Emacs only (copyright assignments are for a single GNU
> package), so you will need to do the paperwork for Guile this time.
>
> Thanks in advance. :-)
>
> Ludo’.
next prev parent reply other threads:[~2023-05-18 0:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 0:48 [PATCH] Extensions for SRFI-171 (Transducers) Colin Woodbury
2022-12-21 10:00 ` Linus Björnstam
2022-12-22 14:33 ` Damien Mattei
2022-12-22 14:52 ` Damien Mattei
2022-12-22 17:32 ` Damien Mattei
2022-12-24 13:25 ` Damien Mattei
2022-12-24 15:28 ` [PATCHv2] " Colin Woodbury
2023-01-14 15:09 ` Ludovic Courtès
2023-01-21 1:48 ` [PATCHv3] " Colin Woodbury
2023-01-23 22:17 ` Ludovic Courtès
2023-01-24 0:21 ` Colin Woodbury
2023-01-24 9:07 ` Ludovic Courtès
2023-05-18 0:36 ` Colin Woodbury [this message]
2023-06-28 12:27 ` Colin Woodbury
2023-08-12 19:37 ` Linus Björnstam
2023-08-13 4:07 ` Colin Woodbury
2023-08-18 10:03 ` Ludovic Courtès
2023-08-18 10:10 ` Colin Woodbury
2023-08-18 13:24 ` Ludovic Courtès
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=07c2b0bb-6c22-da79-2776-362f36ebd19d@fosskers.ca \
--to=colin@fosskers.ca \
--cc=guile-devel@gnu.org \
--cc=linus.bjornstam@veryfast.biz \
--cc=ludo@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).