From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Andrew De Angelis <bobodeangelis@gmail.com>
Cc: emacs-devel@gnu.org, bugs@gnu.support
Subject: Re: New Package: sticky-shell
Date: Wed, 14 Dec 2022 08:41:54 -0500 [thread overview]
Message-ID: <jwv8rja85pa.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAP5CrM2m91apdnrAr8ctO91G1z0knJv1YoGSb+Ab3S+O7-xc-A@mail.gmail.com> (Andrew De Angelis's message of "Wed, 14 Dec 2022 00:23:56 -0500")
>> Step 1 (same as for GNU ELPA): get the copyright paperwork in order.
>> I don't see your name in the FSF's copyright assigners list, so
>> either it's still in process or you haven't started yet.
>> Let me know if you need help with that.
>
> I have not started this. This would be my first contribution to free
> software, so I'm not very familiar with the process. Would greatly
> appreciate it if you could give me a rundown of what to do or just point me
> to the right documentation.
Sure thing. Just fill the form below and email it to the FSF as
instructed so they can send you the relevant paperwork to sign,
> About `sticky-shell-prompt-modifiers`, I welcome any feedback on this
> current approach. My idea was to try to make it simpler for the end
> user, since:
I understand.
Stefan
Please email the following information to assign@gnu.org, and we
will send you the assignment form for your past and future changes.
Please use your full legal name (in ASCII characters) as the subject
line of the message.
----------------------------------------------------------------------
REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES
[What is the name of the program or package you're contributing to?]
Emacs
[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]
[Do you have an employer who might have a basis to claim to own
your changes? Do you attend a school which might make such a claim?]
[For the copyright registration, what country are you a citizen of?]
[What year were you born?]
[Please write your email address here.]
[Please write your postal address here.]
[Which files have you changed so far, and which new files have you written
so far?]
next prev parent reply other threads:[~2022-12-14 13:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 0:05 New Package: sticky-shell Andrew De Angelis
2022-12-12 18:33 ` Philip Kaludercic
2022-12-12 18:45 ` Stefan Monnier
2022-12-12 18:55 ` Akib Azmain Turja
2022-12-13 3:27 ` Jean Louis
2022-12-13 4:07 ` Andrew De Angelis
2022-12-13 14:22 ` Stefan Monnier
2022-12-13 18:24 ` Jean Louis
2022-12-14 5:23 ` Andrew De Angelis
2022-12-14 13:41 ` Stefan Monnier [this message]
2022-12-16 10:20 ` Jean Louis
2022-12-28 15:34 ` Andrew De Angelis
2022-12-30 14:45 ` Jean Louis
2023-02-19 20:56 ` Andrew De Angelis
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=jwv8rja85pa.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=bobodeangelis@gmail.com \
--cc=bugs@gnu.support \
--cc=emacs-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.
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).