unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Trent W. Buck" <trentbuck@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 36759@debbugs.gnu.org
Subject: bug#36759: 26.1; nftables major mode
Date: Mon, 23 May 2022 10:38:50 +1000	[thread overview]
Message-ID: <YorXmuc8WJkEQunp@hera.lan> (raw)
In-Reply-To: <jwv4k28jdsr.fsf-monnier+emacs@gnu.org>

Stefan Monnier wrote:
> >> I'd be happy to add an nftables mode to GNU ELPA, but AFAICT Trent has
> >> not signed the needed paperwork for Emacs.
> > Seems like we forgot about this one
> 
> Yup, sorry.
> 
> > -- Trent's paperwork was completed in December 2021, so we should be
> > able to add nftables to GNU ELPA now.  Stefan?
> 
> Trent, I can't seem to find a Git repository for your code.
> We like to keep the VCS history as much as possible.
> Do you keep `nftables-mode.el` on some public Git somewhere, or maybe in
> a private one?

I don't maintain this code anymore.
My assumption was that it would go into the Emacs repo, and
some other poor bugger(s) would take over ongoing maintenance and improvement.

That's the way Emacs used to work for small modes, and I like/liked that model :-)

If you just want the *old* history, that would probably be in my work's KB repo (private).
Hrm, looks like I never even checked it in!
IIRC I spent about two weeks on nftables, but
I only spent an afternoon on the emacs mode.
So there never really was any change history.

Anyway, what change history I have, is here (snapshot extracted by git filter-repo):

    https://github.com/trentbuck/nft-examples


PS: I realize this is pretty sloppy by modern standards -- sorry!
I only ever got nft support "good enough for now" not "good".





  reply	other threads:[~2022-05-23  0:38 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
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 [this message]
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=YorXmuc8WJkEQunp@hera.lan \
    --to=trentbuck@gmail.com \
    --cc=36759@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).