From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Question on updating to 29.1
Date: Fri, 11 Aug 2023 14:16:07 +0300 [thread overview]
Message-ID: <83cyzthls8.fsf@gnu.org> (raw)
In-Reply-To: <b26c4055-b84a-8533-e8c1-9502fc726899@magnaspesmeretrix.org> (message from PierGianLuca on Fri, 11 Aug 2023 10:45:29 +0200)
> Date: Fri, 11 Aug 2023 10:45:29 +0200
> From: PierGianLuca <luca@magnaspesmeretrix.org>
>
> Thank you Philip and Basile (who gave me advice off-list).
>
> Sorry for not being clear:
>
> > Did you install version 28.1 from a Git checkout or from a tarball?
>
> Tarball. I first *un*installed the Ubuntu pre-packaged Emacs.
>
> I considered fetching from git, but it would add a layer of things that I don't fully understand.
>
> So I can simply re-do what I with 28.1 (with minor changes as Philip warned about), and the new Emacs version will simply replace the old.
>
> Maybe just a short sentence about this can be added to the INSTALL/README files?
A short sentence that basically says there's nothing special to do
when you already have an older version installed? Why is this needed?
In general, if there's no problem, we don't say in the instructions
that there's no problem ;-)
next prev parent reply other threads:[~2023-08-11 11:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 8:11 Question on updating to 29.1 PierGianLuca
2023-08-11 8:21 ` Philip Kaludercic
2023-08-11 8:45 ` PierGianLuca
2023-08-11 8:54 ` Basile Starynkevitch
2023-08-11 10:16 ` Emanuel Berg
2023-08-11 11:20 ` Basile Starynkevitch
2023-08-11 12:20 ` Emanuel Berg
2023-08-17 16:17 ` PierGianLuca
2023-08-17 17:01 ` Corwin Brust
2023-08-17 17:55 ` PierGianLuca
2023-08-17 18:58 ` Basile Starynkevitch
2023-10-05 18:21 ` hw
2023-10-05 18:54 ` Eli Zaretskii
2023-08-18 19:24 ` Philip Kaludercic
2023-08-19 11:05 ` Pop-up font size with lucid toolkit (was: Question on updating to 29.1) PierGianLuca
2023-08-19 11:10 ` Solved: " PierGianLuca
2023-08-19 11:13 ` Gregory Heytings
2023-08-19 11:15 ` PierGianLuca
2023-08-20 12:36 ` Pop-up font size with lucid toolkit Philip Kaludercic
2023-08-20 13:13 ` PierGianLuca
2023-08-21 15:14 ` Philip Kaludercic
2023-08-11 11:16 ` Eli Zaretskii [this message]
2023-08-11 22:04 ` Question on updating to 29.1 Jens Schmidt via Users list for the GNU Emacs text editor
2023-08-12 5:48 ` Eli Zaretskii
2023-08-12 6:08 ` PierGianLuca
2023-08-12 6:23 ` Eli Zaretskii
2023-08-13 12:46 ` Petteri Hintsanen
2023-10-05 11:44 ` Byung-Hee HWANG
2023-10-05 17:17 ` Emanuel Berg
2023-10-06 23:51 ` Byung-Hee HWANG
2023-10-07 7:43 ` Yuri Khan
2023-10-07 12:13 ` Byung-Hee HWANG
2023-10-07 12:28 ` Question on updating to 29.1 (on Ubuntu) PierGianLuca
2023-10-23 16:41 ` Question on updating to 29.1 Basile Starynkevitch
2023-10-06 1:30 ` Emanuel Berg
2023-10-07 6:06 ` జిందం వాఐి
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=83cyzthls8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).