unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: emacs-devel@gnu.org
Subject: New Eglot release
Date: Sat, 04 Mar 2023 20:02:07 +0000	[thread overview]
Message-ID: <87a60sjneo.fsf@gmail.com> (raw)

Hello,

After some significant work done to Eglot in emacs-29 the last few
weeks, I'd like to make the 1.12 release so people can use it from GNU
ELPA in older Emacs versions.

However, one question remains from the merge: where to put
Eglot-specific NEWS describing the latest user-visible changes??

I'm not opposed to putting them in Emacs's own NEWS file, except that
for this Emacs 29 version it'd be a bit akward, since Eglot just made it
in, so the existing NEWS is about Eglot's appearance, not about what
changed recently.

I think, someone suggested /etc/EGLOT-NEWS at the time.  That could
work, I guess.  But would anyone read it?

Also, it'd be nice that it'd go somewhere where the description of the
package in https://elpa.gnu.org/ can pick it up.

João





             reply	other threads:[~2023-03-04 20:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04 20:02 João Távora [this message]
2023-03-05  5:50 ` New Eglot release Eli Zaretskii
2023-03-05  9:09   ` Michael Albinus
2023-03-05 15:30   ` João Távora
2023-03-05 15:37     ` Dmitry Gutov
2023-03-05 15:47     ` Eli Zaretskii
2023-03-05 15:56 ` Philip Kaludercic
2023-03-05 22:15   ` João Távora
2023-03-06 17:33     ` Philip Kaludercic
2023-03-06 17:33     ` Philip Kaludercic
2023-03-07 14:54       ` F. Jason Park
2023-03-10 11:38         ` João Távora
2023-03-10 12:23           ` Eli Zaretskii
2023-03-10 12:50             ` João Távora
2023-03-10 13:06               ` Eli Zaretskii
2023-03-10 13:42                 ` João Távora
2023-03-11 15:11             ` Michael Albinus
2023-03-11 20:16               ` João Távora
2023-03-12  6:23                 ` Eli Zaretskii
2023-03-12 19:12                   ` João Távora

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=87a60sjneo.fsf@gmail.com \
    --to=joaotavora@gmail.com \
    --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).