Mercurial > hg > xemacs-beta

comparison etc/BETA @ 371:cc15677e0335 r21-2b1

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r21-2b1
author cvs
date Mon, 13 Aug 2007 11:03:08 +0200
parents 4f79e16b1112
children 6240c7796c7a
comparison
equal deleted inserted replaced
370:bd866891f083 371:cc15677e0335
195 195
196 Then type `make' and you should have a working XEmacs. 196 Then type `make' and you should have a working XEmacs.
197 197
198 After you have verified that you have a functional editor, fire up 198 After you have verified that you have a functional editor, fire up
199 your favorite mail program and send a build report to 199 your favorite mail program and send a build report to
200 xemacs-build-reports@xemacs.org. The build report should include 200 xemacs-beta@xemacs.org. The build report should include
201 201
202 1. Your hardware configuration (OS version, etc.) 202 1. Your hardware configuration (OS version, etc.)
203 203
204 2. Version numbers of software in use (X11 version, system library 204 2. Version numbers of software in use (X11 version, system library
205 versions if appropriate, graphics library versions if appropriate). 205 versions if appropriate, graphics library versions if appropriate).
221 ================================== 221 ==================================
222 222
223 Patches to XEmacs should be mailed to <xemacs-patches@xemacs.org>. 223 Patches to XEmacs should be mailed to <xemacs-patches@xemacs.org>.
224 Each patch will be reviewed by the patches review board, and will be 224 Each patch will be reviewed by the patches review board, and will be
225 acked and added to the distribution, or rejected with an explanation. 225 acked and added to the distribution, or rejected with an explanation.
226
227 Patches to XEmacs Lisp packages should be sent to the maintainer of
228 the package. If the maintainer is listed as `XEmacs Development Team'
229 patches should be sent to <xemacs-patches@xemacs.org>.
230 226
231 Emailed patches should preferably be sent in MIME format and quoted 227 Emailed patches should preferably be sent in MIME format and quoted
232 printable encoding (if necessary). 228 printable encoding (if necessary).
233 229
234 When making patches, please use the `-u' option, or if your diff 230 When making patches, please use the `-u' option, or if your diff