From: Steve Revilak <steve@srevilak.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Tracking Emacs Development
Date: Mon, 7 Dec 2009 20:13:11 -0500 [thread overview]
Message-ID: <20091208011311.GL11805@srevilak.net> (raw)
In-Reply-To: <jwvk4wyhjef.fsf-monnier+gnu.emacs.help@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
srevilak> What is the best way to follow emacs development? Just
srevilak> check out the trunk [1] and rebuild on a regular basis?
Peter_Dyballa> Yes, and also trying to compile the sources differently
Peter_Dyballa> to see how robust they are. I am using libraries from
Peter_Dyballa> Fink and from MacPorts and see (or better: saw on
Peter_Dyballa> Tiger, on Leopard I haven't had the opportunity yet to
Peter_Dyballa> compile GNU Emacs) differences.
monnier> Yes, that is ideal. If you do that, you'll probably want to
monnier> keep an eye on emacs-devel@gnu.org (it's a fairly
monnier> high-traffic list, tho), for known breakage and things like
monnier> that.
Peter and Stefan,
Thank you for the suggestions. I'll go back to building from the
trunk (and pretest versions, when they're available).
Steve
[-- Attachment #2: Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2009-12-08 1:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091207181006.3C39943CE1@mxperim3.sea5.speakeasy.net>
[not found] ` <20091206170639.0B08BB3563@mxperim2.sea5.speakeasy.net>
[not found] ` <mailman.12400.1260152858.2239.help-gnu-emacs@gnu.org>
2009-12-07 15:55 ` Tracking Emacs Development Stefan Monnier
2009-12-08 1:13 ` Steve Revilak [this message]
[not found] <mailman.12251.1259993776.2239.help-gnu-emacs@gnu.org>
2009-12-05 19:01 ` Fullscreen Mode, Emacs 23 and OS X Stefan Monnier
2009-12-06 16:43 ` Steve Revilak
2009-12-07 2:27 ` Tracking Emacs Development (was: Fullscreen Mode, Emacs 23 and OS X) Steve Revilak
2009-12-07 9:32 ` Peter Dyballa
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=20091208011311.GL11805@srevilak.net \
--to=steve@srevilak.net \
--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.