From: Hans Lonsdale <hanslonsdale@mailfence.com>
To: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: Getting latest development version
Date: Sat, 26 Nov 2022 20:06:36 +0100 (CET) [thread overview]
Message-ID: <1963649397.63084.1669489596756@orville.co-bxl> (raw)
In-Reply-To: <83zgcdr18d.fsf@gnu.org>
> ----------------------------------------
> From: Eli Zaretskii <eliz@gnu.org>
> Sent: Sat Nov 26 19:59:14 CET 2022
> To: <help-gnu-emacs@gnu.org>
> Subject: Re: Getting latest development version
>
>
> > Date: Sat, 26 Nov 2022 19:07:50 +0100 (CET)
> > From: Hans Lonsdale via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
> >
> > Have been trying to get the latest development version of emacs, but still getting "emacs-29.0.50".
>
> That is the latest development version, as of today.
Was under the impression that development versions happen directly when changes to the code are committed.
> > I still have difficulty getting the latest version. Would you be so kind to do something about this, so that
> > it is not so perplexing on how to get emacs versions, including development versions, if you please.
>
> For the latest version, just clone the Git repository and build it. That's
> it.
Could you add more details (commands for download) directly on "software/emacs/download.html" on
how to get the various possibilities (releases, development version). Currently everything is dispersed
in the emacs website and the savannah website. It is quite a strain to have to go through searching for things.
https://www.gnu.org/software/emacs/download.html
--
Sent with https://mailfence.com
Secure and private email
next prev parent reply other threads:[~2022-11-26 19:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 18:07 Getting latest development version Hans Lonsdale via Users list for the GNU Emacs text editor
2022-11-26 18:53 ` Emanuel Berg
2022-11-26 18:59 ` Eli Zaretskii
2022-11-26 19:06 ` Hans Lonsdale [this message]
2022-11-27 8:13 ` Eli Zaretskii
2022-11-27 8:38 ` Jean Louis
2022-11-27 9:09 ` Eli Zaretskii
2022-11-26 19:10 ` Jean Louis
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=1963649397.63084.1669489596756@orville.co-bxl \
--to=hanslonsdale@mailfence.com \
--cc=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.
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.