From: Corwin Brust <corwin@bru.st>
To: Zan Owsley <zanowsley@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 74663@debbugs.gnu.org
Subject: bug#74663: Emacs crashes with Segfault while doing basic code editing
Date: Sat, 14 Dec 2024 10:37:56 -0600 [thread overview]
Message-ID: <CAJf-WoROiHdBH_hmmSXgOFMz-bkxnL9E9i_LH1S2LbtjUfeY9A@mail.gmail.com> (raw)
In-Reply-To: <1c38f778-af49-43bb-a331-cd228a70b6c4@gmail.com>
On Sat, Dec 14, 2024 at 10:04 AM Zan Owsley <zanowsley@gmail.com> wrote:
>
> P.S. You might hear more from me in the future. I think I'd like to get
> involved with contributing to Emacs. I'm not elisp expert yet, but I'm
> getting better. :)
>
Zan,
What a wonderful email - thank you for your kind words toward Eli and
all the hard-work that has gone into Emacs to prepare for the release
of Emacs 30! I completely agree and it's nice to see these messages
of encouragement for the thoughtful and diligent devs that bring us
Emacs :)
Can I invite you to complete the Copyright Assignment paperwork to
grant the FSF ownership of any code/changes you provide for Emacs?
This is nearly always a requirement to merge your contributions.
Meanwhile, "doing the paperwork" doesn't obligate you to contribute:
it just removes a barrier should you wish to do so.
If you'd like to do that please reply back to say so and, I expect,
Eli (or another Maint) will send over the forms by private email.
Thanks again for sharing your comments; glad you are loving Emacs 30!
next prev parent reply other threads:[~2024-12-14 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 18:35 bug#74663: Emacs crashes with Segfault while doing basic code editing Zan Owsley
2024-12-03 13:10 ` Eli Zaretskii
[not found] ` <CAFeMKvwPyAqeossiQMjqcRoq8GzKd3kVpkXK-gMDHLQhd2FXpg@mail.gmail.com>
2024-12-14 9:44 ` Eli Zaretskii
2024-12-14 16:04 ` Zan Owsley
2024-12-14 16:37 ` Corwin Brust [this message]
2024-12-14 17:48 ` Zan Owsley
2024-12-14 20:04 ` Eli Zaretskii
2024-12-14 16:49 ` Eli Zaretskii
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=CAJf-WoROiHdBH_hmmSXgOFMz-bkxnL9E9i_LH1S2LbtjUfeY9A@mail.gmail.com \
--to=corwin@bru.st \
--cc=74663@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=zanowsley@gmail.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).