unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Stephen Leake <stephen_leake@stephe-leake.org>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: * lisp/progmodes/eglot.el (eglot--connect): Use project-name
Date: Fri, 25 Nov 2022 09:28:51 +0000	[thread overview]
Message-ID: <CALDnm518SPnvgJCOfFqrcmDypnrP8icJLsTR1kWNW-GXk3_KSA@mail.gmail.com> (raw)
In-Reply-To: <97e095be-4214-6689-e605-4795a9928fac@yandex.ru>

[-- Attachment #1: Type: text/plain, Size: 846 bytes --]

  On Thu, Nov 24, 2022 at 9:35 PM Dmitry Gutov <dgutov@yandex.ru> wrote:
>
> On 24/11/22 16:43, João Távora wrote:
> > So you must merely bump the "Version:" of the project.el package in
> > that file and then make eglot.el reference the new version in its
> > "Package-Requires:".
>
> You could also wait until the new version if out and then bump the
> required version and simplify.

Not sure I understood correctly, but that's two changes instead of one,
and unnecessary "VC churn".  Also, I forgot to mention that adding
project-name _without_ the fboundp is fine even without any version
bumping.  It's only when eglot.el is bumped after that that we must
ensure project.el is also bumped.

Is there a regular project.el release schedule? Eglot doesn't really have
one itself.  It's "whenever it's convenient".

João

[-- Attachment #2: Type: text/html, Size: 1079 bytes --]

  reply	other threads:[~2022-11-25  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 14:43 * lisp/progmodes/eglot.el (eglot--connect): Use project-name João Távora
2022-11-24 21:30 ` [SPAM UNSURE] " Stephen Leake
2022-11-24 21:35 ` Dmitry Gutov
2022-11-25  9:28   ` João Távora [this message]
2022-11-25 15:14     ` Dmitry Gutov

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=CALDnm518SPnvgJCOfFqrcmDypnrP8icJLsTR1kWNW-GXk3_KSA@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=stephen_leake@stephe-leake.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).