From: Dmitry <dmitry@gutov.dev>
To: "Eli Zaretskii" <eliz@gnu.org>, "Philip Kaludercic" <philipk@posteo.net>
Cc: emacs-devel@gnu.org, joaotavora@gmail.com
Subject: Re: emacs-29 44ebd9cbd56 2/2: Eglot: explain how to update Eglot in manual (bug#62720)
Date: Sat, 29 Apr 2023 12:54:17 +0300 [thread overview]
Message-ID: <4c4850f1-0f29-41f9-a2f9-5e209650ee0d@app.fastmail.com> (raw)
In-Reply-To: <83zg6rowl7.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
On Sat, Apr 29, 2023, at 12:40 PM, Eli Zaretskii wrote:
> > From: Philip Kaludercic <philipk@posteo.net>
> > Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org, joaotavora@gmail.com
> > Date: Sat, 29 Apr 2023 09:08:22 +0000
> >
> > What do you think about the approach of adding package.el to ELPA, and
> > then being able to fix the issue of package-upgrade/install that way?
>
> We should be careful about that: it could produce bootstrap-type
> problems, since package.el is itself required for fetching stuff from
> ELPA.
Right. I mentioned exactly that concern in the other bug thread.
[-- Attachment #2: Type: text/html, Size: 1144 bytes --]
next prev parent reply other threads:[~2023-04-29 9:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <168263878553.23108.4718240877999827191@vcs2.savannah.gnu.org>
[not found] ` <20230427233949.44D31C22A13@vcs2.savannah.gnu.org>
2023-04-27 23:52 ` emacs-29 44ebd9cbd56 2/2: Eglot: explain how to update Eglot in manual (bug#62720) Dmitry Gutov
2023-04-28 0:35 ` João Távora
2023-04-28 0:40 ` Dmitry Gutov
2023-05-03 22:48 ` Dmitry Gutov
2023-05-03 23:31 ` João Távora
2023-05-03 23:39 ` Dmitry Gutov
2023-05-04 0:50 ` João Távora
2023-05-04 0:56 ` Dmitry
2023-05-04 1:09 ` João Távora
2023-05-04 9:05 ` Dmitry Gutov
2023-05-05 14:01 ` João Távora
2023-05-05 15:06 ` Dmitry Gutov
2023-04-28 4:37 ` Eli Zaretskii
2023-04-28 14:25 ` Philip Kaludercic
2023-04-28 15:30 ` Dmitry Gutov
2023-04-28 18:12 ` Philip Kaludercic
2023-04-29 0:52 ` Dmitry Gutov
2023-04-29 6:45 ` Eli Zaretskii
2023-04-29 10:01 ` Dmitry
2023-04-29 10:13 ` Philip Kaludercic
2023-04-29 11:51 ` Dmitry
2023-04-29 10:34 ` Eli Zaretskii
2023-04-29 9:08 ` Philip Kaludercic
2023-04-29 9:40 ` Eli Zaretskii
2023-04-29 9:54 ` Dmitry [this message]
2023-04-29 10:15 ` Philip Kaludercic
2023-04-29 12:52 ` João Távora
2023-04-29 13:10 ` Po Lu
2023-04-30 12:12 ` Philip Kaludercic
2023-04-30 17:43 ` Michael Albinus
2023-05-01 2:09 ` João Távora
2023-05-01 7:34 ` Philip Kaludercic
2023-05-02 7:56 ` Robert Pluim
2023-05-05 5:13 ` Philip Kaludercic
2023-05-05 6:23 ` Robert Pluim
2023-05-02 20:35 ` João Távora
2023-04-29 6:42 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4c4850f1-0f29-41f9-a2f9-5e209650ee0d@app.fastmail.com \
--to=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=philipk@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.