From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Upgrading Emacs from Git
Date: Thu, 11 Feb 2016 09:07:31 -0500 [thread overview]
Message-ID: <jwvh9hfpchn.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: 20160210165107.GB14358@len.workgroup
>> a quick question: I compiled Emacs from Git and now want to upgrade it.
>> Is it enough to pull a fresh version and then make && make install?
> A simple git pull is all you need to do in order to get new
> commits. After that do a make && make install.
FWIW, I just do "make" and never run "make install".
Stefan
next prev parent reply other threads:[~2016-02-11 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 10:22 Upgrading Emacs from Git Marcin Borkowski
2016-02-10 16:51 ` Gregor Zattler
2016-02-11 14:07 ` Stefan Monnier [this message]
2016-02-10 17:27 ` Eli Zaretskii
2016-02-10 18:20 ` Óscar Fuentes
2016-02-11 0:52 ` Emanuel Berg
2016-02-11 1:24 ` Óscar Fuentes
2016-02-11 1:55 ` Emanuel Berg
[not found] ` <mailman.4359.1455152116.843.help-gnu-emacs@gnu.org>
2016-02-11 1:25 ` P. A. López-Valencia
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=jwvh9hfpchn.fsf-monnier+gmane.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--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).