From: Eli Zaretskii <eliz@gnu.org>
To: Andrew De Angelis <bobodeangelis@gmail.com>
Cc: luangruo@yahoo.com, 60703@debbugs.gnu.org
Subject: bug#60703: Patches to xwidget code
Date: Sat, 21 Jan 2023 17:41:15 +0200 [thread overview]
Message-ID: <83fsc3lwtg.fsf@gnu.org> (raw)
In-Reply-To: <CAP5CrM2=gtX3RfyiLDmXTRNK_WKTTUz3_jSn0vxm0GJ96xzG7Q@mail.gmail.com> (message from Andrew De Angelis on Sat, 21 Jan 2023 10:32:19 -0500)
> From: Andrew De Angelis <bobodeangelis@gmail.com>
> Date: Sat, 21 Jan 2023 10:32:19 -0500
> Cc: luangruo@yahoo.com, 60703@debbugs.gnu.org
>
> Sorry about the confusion!
> Looks like I missed that reply.
> Some quick clarification though: the first assignment I sent out was for some modifications to shell.el
> (bug#60385; see also the thread "New Package: sticky-shell" in emacs-devel: I had a package idea and it
> was mentioned to add it as a feature instead). I then 1) missed the reply from copyright-clerk@fsf.org, 2)
> assumed I'd need an additional copyright assignment for the xwidget-patch, as it concerns different files.
> Is the first assignment good enough for all subsequent files I change? If that's the case I'll go ahead and sign
> it and send it back asap. Just wanted to make sure I'm following the correct procedure.
The assignment will be good for all your future contributions to
Emacs, but first you need to do what the copyright clerk asked you to
do: print the PDF form, sign it, scan it, and email it back. Then
you'll get another email saying that your paperwork is complete, and
then we can accept contributions from you.
Thanks.
next prev parent reply other threads:[~2023-01-21 15:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 5:14 bug#60703: Patches to xwidget code Andrew De Angelis
2023-01-10 9:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87cz7mhfrr.fsf@yahoo.com>
2023-01-10 13:40 ` Eli Zaretskii
2023-01-10 23:33 ` Andrew De Angelis
2023-01-11 1:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-21 6:13 ` Andrew De Angelis
2023-01-21 7:16 ` Eli Zaretskii
2023-01-21 15:32 ` Andrew De Angelis
2023-01-21 15:41 ` Eli Zaretskii [this message]
2023-01-26 23:45 ` Andrew De Angelis
2023-01-27 0:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-19 21:00 ` Andrew De Angelis
2023-02-20 2:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-20 11:47 ` Eli Zaretskii
2023-02-21 5:24 ` Andrew De Angelis
2023-02-22 13:27 ` Eli Zaretskii
2023-02-24 3:47 ` Andrew De Angelis
2023-03-02 10:57 ` Eli Zaretskii
2023-03-04 23:00 ` Andrew De Angelis
2023-03-05 0:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83fsc3lwtg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60703@debbugs.gnu.org \
--cc=bobodeangelis@gmail.com \
--cc=luangruo@yahoo.com \
/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).