unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: trentbuck@gmail.com (Trent W. Buck), Lars Ingebrigtsen <larsi@gnus.org>
Cc: 36759@debbugs.gnu.org
Subject: bug#36759: 26.1; nftables major mode
Date: Wed, 22 Sep 2021 22:22:21 -0400	[thread overview]
Message-ID: <jwvr1dg590l.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ee9gs448.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 22 Sep 2021 23:16:23 +0200")

> I think perhaps this makes more sense in GNU ELPA than in Emacs core
> (since editing nftables files is a somewhat specialised task), and I
> looked into putting it there, but I'm still not quite sure how.  :-)
>
> So I've added Stefan to the CCs -- could you do the right thing here?

I'd be happy to add an nftables mode to GNU ELPA, but AFAICT Trent has
not signed the needed paperwork for Emacs.
Trent, would you be OK signing that copyright paperwork?
If so, please fill the form below and send it to the FSF as instructed
so they can send you the appropriate paperwork to sign.


        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?]






  reply	other threads:[~2021-09-23  2:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22  7:45 bug#36759: 26.1; nftables major mode Trent W. Buck
2019-08-10  8:07 ` Eli Zaretskii
2019-08-12  1:16   ` Trent W. Buck
2020-09-05  1:13     ` Stefan Kangas
2020-09-05  4:34       ` Trent W. Buck
2021-09-22 21:16 ` Lars Ingebrigtsen
2021-09-23  2:22   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-09-24  2:49     ` Trent W. Buck
2022-05-02  8:40     ` Lars Ingebrigtsen
2022-05-02 12:55       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23  0:38         ` Trent W. Buck
2022-05-23 12:21           ` Stefan Monnier 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=jwvr1dg590l.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=36759@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=trentbuck@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).