From: Jason Earl <jearl@notengoamigos.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Upgrading suggestions
Date: Sun, 23 Oct 2011 21:38:40 -0600 [thread overview]
Message-ID: <8739ejqcsf.fsf@notengoamigos.org> (raw)
In-Reply-To: j82j09$fun$3@reader1.panix.com
On Sun, Oct 23 2011, David Combs wrote:
> In article <87fwj8tadw.fsf@notengoamigos.org>,
> Jason Earl <jearl@notengoamigos.org> wrote:
>> <snip>
>>I think that the best way to deal with this is to run a version of Emacs
>>straight out of bzr. Not only does this get you the newest toys before
>>everyone else, but it also allows you access to the new configuration
>>changes and such piecemeal instead of having to make a big jump from one
>>version to the next.
>>
>>If something does break your configuration, you can even complain on
>>emacs-devel while the issue is still fresh on the developers mind.
>>
>>Jason
>
> What is "bzr"? (A misspelled ".bz"?)
>
> And where is this early version located?
>
> Thanks!
>
> David
bzr is the version control system that the Emacs project uses.
http://bazaar.canonical.com/en/
To get a copy of the Emacs trunk in a folder named "emacs-devel" you
would do (after installing bzr):
bzr branch bzr://bzr.savannah.gnu.org/emacs/trunk emacs-devel
For more information there is a wiki page here:
http://www.emacswiki.org/emacs/BzrForEmacsDevs
Basically I am encouraging you to use the development version of Emacs.
It is much snazzier than the released version, and if the Emacs
developers break your configuration you are in a good position to tell
them about it.
Jason
next parent reply other threads:[~2011-10-24 3:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5127.1317749352.939.help-gnu-emacs@gnu.org>
[not found] ` <87fwj8tadw.fsf@notengoamigos.org>
[not found] ` <j82j09$fun$3@reader1.panix.com>
2011-10-24 3:38 ` Jason Earl [this message]
2011-10-04 17:28 Upgrading suggestions Perry Smith
2011-10-04 18:09 ` Jambunathan K
2011-10-04 20:32 ` S Boucher
2011-10-06 19:19 ` Ken Goldman
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=8739ejqcsf.fsf@notengoamigos.org \
--to=jearl@notengoamigos.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).