From: Eli Zaretskii <eliz@gnu.org>
To: Nicolas Martyanoff <nicolas@n16f.net>
Cc: nicolas@n16f.net, emacs-devel@gnu.org, monnier@iro.umontreal.ca
Subject: Re: [PATCH] em-cmpl: fix completion of command paths
Date: Thu, 26 Jan 2023 14:58:57 +0200 [thread overview]
Message-ID: <834jsde9ke.fsf@gnu.org> (raw)
In-Reply-To: <87lelp7agn.fsf@valhala.localdomain> (message from Nicolas Martyanoff on Thu, 26 Jan 2023 13:21:28 +0100)
> From: Nicolas Martyanoff <nicolas@n16f.net>
> Cc: nicolas@n16f.net, emacs-devel@gnu.org, monnier@iro.umontreal.ca
> Date: Thu, 26 Jan 2023 13:21:28 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Date: Thu, 26 Jan 2023 08:02:51 +0200
> >> From: Eli Zaretskii <eliz@gnu.org>
> > Oops! I now see that we don't have a copyright assignment from you,
> > which we need for such a substantial contribution. Would you like to
> > start your legal paperwork, so that we could accept this contribution?
> > If so, I will send you the form to fill.
>
> I started the process while sending the patch. I sent the signed
> documents to Craig Topham two minutes ago.
Great, then I will install the changes when the paperwork is complete.
Thanks.
next prev parent reply other threads:[~2023-01-26 12:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 12:19 [PATCH] em-cmpl: fix completion of command paths Nicolas Martyanoff
2023-01-07 12:23 ` Nicolas Martyanoff
2023-01-13 10:59 ` Nicolas Martyanoff
2023-01-25 17:03 ` Stefan Monnier
2023-01-25 17:15 ` Eli Zaretskii
2023-01-25 20:32 ` [PATCH] Update compat Nicolas Martyanoff
[not found] ` <87bkmmwcwx.fsf@valhala.localdomain>
2023-01-26 6:02 ` [PATCH] em-cmpl: fix completion of command paths Eli Zaretskii
2023-01-26 9:06 ` Eli Zaretskii
2023-01-26 12:21 ` Nicolas Martyanoff
2023-01-26 12:58 ` Eli Zaretskii [this message]
2023-01-28 0:11 ` Stefan Monnier
2023-01-28 8:27 ` Eli Zaretskii
2023-01-28 0:12 ` Stefan Monnier
2023-01-25 21:50 ` Jim Porter
2023-02-08 6:06 ` Jim Porter
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834jsde9ke.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nicolas@n16f.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).