Mercurial > emacs
view admin/notes/BRANCH @ 109507:1277fe6717c9
New make target for Windows platform: make dist (bug#6602)
* admin/admin.el: Write version number to nt/makefile.w32-in.
* admin/nt/makedist.bat: Remove; replaced with `zipdist.bat'
in the nt/ directory.
* admin/nt/README.W32: Relocate to nt/ directory.
* etc/NEWS: Document new --distfiles configure.bat option and
`dist' make target on Windows.
* nt/INSTALL: Document new dist target and add section about
creating binary distributions.
* nt/configure.bat: New parameter `--distfiles'.
* nt/makefile.w32-in: Add version number, new target `dist'.
Add new target `install-shortcuts'.
* nt/zipdist.bat: New file; create zipped binary distribution,
replaces admin/nt/makedist.bat.
author | Juanma Barranquero <lekktu@gmail.com> |
---|---|
date | Sat, 24 Jul 2010 15:35:31 +0200 |
parents | afb992a317bd |
children |
line wrap: on
line source
You can view the available Emacs branches at http://bzr.savannah.gnu.org/r/emacs/ Development normally takes places on the trunk. Sometimes specialized features are developed on separate branches before possibly being merged to the trunk. Development is discussed on the emacs-devel mailing list. Sometime before the release of a new major version of Emacs (eg 23.2), a "feature freeze" is imposed on the trunk. No new features may be added after this point. This is usually some months before the release. Shortly before the release, a release branch is created, and the trunk is then free for development. For example, "emacs-23" for Emacs 23.2 and later, "EMACS_23_1_RC" for 23.1, "EMACS_22_BASE" for 22.x, and "EMACS_21_1_RC" for 21.x. Consult emacs-devel for exactly what kinds of changes are allowed on what branch at any time. If you are looking at this file in a branch other than the trunk, there may be some branch-specific documentation below this line. ________________________________________________________________________