Mercurial > hg > xemacs-beta

comparison etc/MAILINGLISTS @ 359:8e84bee8ddd0 r21-1-9

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r21-1-9
author cvs
date Mon, 13 Aug 2007 10:57:55 +0200
parents f220cc83d72e
children cc15677e0335
comparison
equal deleted inserted replaced
358:fed6e0f6a03a 359:8e84bee8ddd0
1 1
2 XEmacs Electronic Mailing Lists. Last Modified: 1997-01-13 2 XEmacs Electronic Mailing Lists. Last Modified: 1999-11-08
3 3
4 XEmacs has its own mailing list and newsgroup which are distinct from 4 XEmacs has its own mailing lists and newsgroup which are distinct from
5 the FSF GNU Emacs mailing lists and newsgroups. The mailing list is: 5 the FSF GNU Emacs mailing lists and newsgroups. The mailing lists are:
6 6
7 xemacs@xemacs.org For reporting all bugs in XEmacs, including bugs 7 xemacs@xemacs.org comp.emacs.xemacs bi-directional gateway.
8 in the compilation and installation procedures. 8
9 Also for all random questions and conversation 9 xemacs is an open list for discussion and bug reporting for
10 about XEmacs. 10 XEmacs. This mailing list is bi-directionally gatewayed with the
11 USENET newsgroup comp.emacs.xemacs.
11 12
12 This mailing list is bidirectionally gatewayed into the USENET newsgroup 13 xemacs-announce@xemacs.org XEmacs Announcements.
13 comp.emacs.xemacs.
14 14
15 To be added or removed from this mailing list, send mail to 15 xemacs-announce is a read-only, low volume list for announcements
16 xemacs-request@xemacs.org (If it is possible for you to read the 16 concerning the XEmacs project and new releases of the XEmacs
17 messages via the newsgroup, we would prefer that; the fewer people there 17 software.
18 are on the mailing list, the less trouble it is to maintain.) 18
19 xemacs-beta@xemacs.org XEmacs Beta Testers.
20
21 xemacs-beta is an open list for bug reports and general
22 communication about beta versions of XEmacs.
23
24 xemacs-build-reports@xemacs.org XEmacs Build Report Submissions.
25
26 xemacs-build-reports is an open list for submission of build-reports
27 on beta versions of XEmacs. For information on what the
28 build-reports should contain, please see the `etc/BETA' file which
29 is included in each beta distribution.
30
31 xemacs-cvs@xemacs.org XEmacs CVS Commit Notices.
32
33 xemacs-cvs is a read-only list for notices and information on what
34 has been committed to the XEmacs CVS trees, by whom, and for
35 what. (For more information on the XEmacs CVS Archive:
36 http://cvs.xemacs.org/.)
37
38 xemacs-mule@xemacs.org XEmacs International Extensions.
39
40 xemacs-mule is an open mailing list for discussion of International
41 extensions to XEmacs including Mule, XIM, I18n issues, etc, and is
42 not confined to developmental issues. This list is not restricted
43 to English, postings in all languages are welcome.
44
45 xemacs-nt@xemacs.org XEmacs on Windows NT/98/95.
46
47 xemacs-nt is a developer's only mailing list and is intended for
48 people who wish to work actively on the porting of XEmacs to
49 Microsoft Windows NT and Microsoft Windows 98/95.
50
51 xemacs-patches@xemacs.org XEmacs Patch Submissions.
52
53 xemacs-patches is an open, moderated list for submission of patches
54 to the XEmacs distribution and its packages. Anyone may subscribe or
55 submit to xemacs-patches, but all submissions are reviewed by the
56 list moderator before they are distributed to the list. Discussion
57 is not appropriate on xemacs-patches.
58
59 xemacs-users-ja@xemacs.org XEmacs (Japanese).
60
61 xemacs-users-ja is an open list for discussion and bug reporting for
62 XEmacs. Japanese is the preferred language of discussion. It is not
63 gated to comp.emacs.xemacs or the xemacs list. For fastest
64 response, bugs not specifically related to Japanese or Mule features
65 should be reported on xemacs (in English).
66
67 xemacs-beta-ja@xemacs.org XEmacs Beta (Japanese).
68
69 xemacs-beta-ja is an open list for bug reports and general
70 communication about beta versions of XEmacs, especially features
71 related to Mule and Japanese-handling. Japanese is the preferred
72 language of discussion. Bugs not specifically related to Japanese or
73 Mule features should be reported on xemacs-beta (in English). Please
74 consider sending bug reports on Mule to xemacs-mule, in English.
75
76 The most up to date information on the mailing lists can always be
77 found at http://www.xemacs.org/.
78
79 Subscriptions:
80
81 Subscription to all the lists is accomplished by sending an e-mail
82 message to LISTNAME-request@xemacs.org with `subscribe' (without the
83 quotes) as the BODY of the message.
84
85 To unsubscribe, send an e-mail to LISTNAME-request@xemacs.org with
86 `unsubscribe' (without the quotes) as the BODY of the message.
87
88 List Archives:
89
90 A browsable and searchable archive of these lists is available at
91 http://www.xemacs.org/list-archives/.
92
93 Problems:
94
95 Any comments, questions, or complaints about the lists should be
96 brought to the attention of the XEmacs Mailing List Manager
97 <list-manager@xemacs.org>.
98
99 -----------------------------------------------------------------------
100
101 GNU Project Electronic Mailing Lists and gnUSENET Newsgroups:
102
103 The XEmacs project is separate from and not managed by the GNU
104 project. The latest information about the GNU project mailing lists
105 can be found at ftp://ftp.gnu.org/gnu/GNUinfo/MAILINGLISTS
19 106
20 Please do NOT send messages about problems with XEmacs to the FSF GNU 107 Please do NOT send messages about problems with XEmacs to the FSF GNU
21 Emacs newsgroups and mailing lists (listed below) unless you are sure 108 Emacs newsgroups and mailing lists unless you are sure that the
22 that the problem you are reporting is a problem with both versions of 109 problem you are reporting is a problem with both versions of GNU
23 GNU Emacs. People who aren't subscribed to the XEmacs mailing list most 110 Emacs. People who aren't subscribed to the XEmacs mailing list most
24 likely are not interested in hearing about problems with it. 111 likely are not interested in hearing about problems with it.
25 112
26 The XEmacs mailing list is archived at ftp://ftp.xemacs.org/pub/xemacs/mlists/.
27
28 See the file etc/BETA for more information about mailing lists for use
29 by beta testers and XEmacs developers.
30
31 IMPORTANT IMPORTANT IMPORTANT:
32
33 Aside from the names of the mailing lists and newsgroups corresponding
34 to this version of Emacs, the guidelines enumerated below still apply.
35 Please read them before sending a message.
36
37 -----------------------------------------------------------------------
38 GNU Project Electronic Mailing Lists and gnUSENET Newsgroups
39 Last Updated 1 July 97
40
41 Please report improvements to: gnu@prep.ai.mit.edu
42
43 * GNU mailing lists are also distributed as USENET news groups
44
45 The mailing lists are gated both ways with the gnu.all newsgroups at
46 ohio-state.edu. The one-to-one correspondence is indicated below. If
47 you don't know if your site is on USENET, ask your system administrator.
48 If you are a USENET site and don't get the gnu.all newsgroups, please
49 ask your USENET administrator to get them. If he has your feeds ask
50 their feeds, you should win. And everyone else wins: newsgroups make
51 better use of the limited bandwidth of the computer networks and your
52 home machine than mailing list traffic; and staying off the mailing
53 lists make better use of the people who maintain the lists and the
54 machines that the GNU people working with rms use (i.e. we have more
55 time to produce code!!). Thanx.
56
57 * Getting the mailing lists directly
58
59 If several users at your site or local network want to read a list and
60 you aren't a USENET site, Project GNU would prefer that you would set up
61 one address that redistributes locally. This reduces overhead on our
62 people and machines, your gateway machine, and the network(s) used to
63 transport the mail from us to you.
64
65 * How to subscribe to and report bugs in mailing lists
66
67 Send messages ABOUT these lists, such as reports of mail problems, or
68 requests to be added or removed, to help-gnu-emacs-request (or
69 info-gnu-request, bug-gdb-request, etc.), NOT to info-gnu-emacs (or
70 info-gnu, etc.). These <LIST_NAME>-request addresses go only to the
71 people who can do something about your requests or problems, and thus
72 avoids disturbing everyone else.
73
74 Note that all GNU mailing lists are maintained by volunteers. They get
75 behind occasionally. Wait at least 3 or 4 days before asking again.
76 Thanks!
77
78 Many of the GNU mailing lists are very large and are received by many
79 people. Please don't send them anything that is not seriously important
80 to all their readers. All GNU mailing lists are unmoderated, mail
81 reflectors, except info-gnu, info-gnu-emacs, info-gcc, info-g++,
82 info-gnu-fortran.
83
84 All addresses below are in internet format. Consult the mail guru for
85 your computer to figure out address syntaxes from other networks. From
86 UUCP machines:
87 ..!ucbvax!prep.ai.mit.edu!ADDRESS
88 ..!uunet!prep.ai.mit.edu!ADDRESS
89
90 If a message you mail to a list is returned from a MAILER-DAEMON (often
91 with the line:
92 ----- Transcript of session follows -----
93 don't resend the message to the list. All this return means is that
94 your original message failed to reach a few addresses on the list. Such
95 messages are NEVER a reason to resend a piece of mail a 2nd time. This
96 just bothers all (less the few delivery failures (which will probably
97 just fail again!)) of the readers of the list with a message they have
98 already seen. It also wastes computer and network resources.
99
100 It is appropriate to send these to the -request address for a list, and
101 ask them to check the problem out.
102
103 * Send Specific Requests for Information to: gnu@prep.ai.mit.edu
104
105 Specific requests for information about obtaining GNU software, or GNU
106 activities in Cambridge and elsewhere can be directed to:
107 gnu@prep.ai.mit.edu
108
109 * General Information about all lists
110
111 Please keep each message under 25,000 characters. Some mailers bounce
112 messages that are longer than this. If your message is long, it is
113 generally better to send a message offering to make the large file
114 available to only those people who want it (e.g. mailing it to people
115 who ask, or putting it up for FTP). In the case of gnu.emacs.sources,
116 somewhat larger postings (up to 10 parts of no more than 25,000
117 characters each) are acceptable (assuming they are likely to be of
118 interest to a reasonable number of people); if it is larger than that
119 have it added to archive.cis.ohio-state.edu (the GNU Emacs Lisp ftp and
120 uucp archive on and announce) its location there. Good bug reports are
121 short. See section '* General Information about bug-* lists and ...'
122 for further details.
123
124 Most of the time, when you reply to a message sent to a list, the reply
125 should not go to the list. But most mail reading programs supply, by
126 default, all the recipients of the original as recipients of the reply.
127 Make a point of deleting the list address from the header when it does
128 not belong. This prevents bothering all readers of a list, and reduces
129 network congestion.
130
131 The GNU mailing lists and newsgroups, like the GNU project itself, exist
132 to promote the freedom to share software. So don't use these lists to
133 promote or recommend non-free software. (Using them to post ordering
134 information is the ultimate faux pas.) If there is no free program to
135 do a certain task, then somebody should write one!
136
137 * General Information about info-* lists
138
139 These lists and their newsgroups are meant for important announcements.
140 Since the GNU project uses software development as a means for social
141 change, the announcements may be technical or political.
142
143 Most GNU projects info-* lists (and their corresponding gnu.*.announce
144 newsgroups) are moderated to keep their content significant and
145 relevant. If you have a bug to report, send it to the bug-* list. If
146 you need help on something else and the help-* list exists, ask it.
147
148 See section '* General Information about all lists'.
149
150 * General Information about help-* lists
151
152 These lists (and their newsgroups) exist for anyone to ask questions
153 about the GNU software that the list deals with. The lists are read by
154 people who are willing to take the time to help other users.
155
156 When you answer the questions that people ask on the help-* lists, keep
157 in mind that you shouldn't answer by promoting a proprietary program as
158 a solution. The only real solutions are the ones all the readers can
159 share.
160
161 If a program crashes, or if you build it following the standard
162 procedure on a system on which it is supposed to work and it does not
163 work at all, or if an command does not behave as it is documented to
164 behave, this is a bug. Don't send bug reports to a help-* list; mail
165 them to the bug-* list instead.
166
167 See section '* General Information about all lists'.
168
169 * General Information about bug-* lists and reporting program bugs
170
171 If you think something is a bug in a program, it might be one; or, it
172 might be a misunderstanding or even a feature. Before beginning to
173 report bugs, please read the section ``Reporting Emacs Bugs'' toward the
174 end of the GNU Emacs reference manual (or node Emacs/Bugs in Emacs's
175 built-in Info system) for a discussion of how and when to send in bug
176 reports. For GNU programs other than GNU Emacs, also consult their
177 documentation for their bug reporting procedures. Always include the
178 version number of the GNU program, as well as the operating system and
179 machine the program was ran on (if the program doesn't have a version
180 number, send the date of the latest entry in the file ChangeLog). For
181 GNU Emacs bugs, type "M-x emacs-version". A debugger backtrace of any
182 core dump, can also be useful. Be careful to separate out hypothesis
183 from fact! For bugs in GNU Emacs lisp, set variable debug-on-error to
184 t, and re-enter the command(s) that cause the error message; Emacs will
185 pop up a debug buffer if something is wrong; please include a copy of
186 the buffer in your bug report. Please also try to make your bug report
187 as short as possible; distill the problem to as few lines of code and/or
188 input as possible. GNU maintainers give priority to the shortest, high
189 quality bug reports.
190
191 Please don't send in a patch without a test case to illustrate the
192 problem the patch is supposed to fix. Sometimes the patches aren't
193 correct or aren't the best way to do the job, and without a test case
194 there is no way to debug an alternate fix.
195
196 The purpose of reporting a bug is to enable the bug to be fixed for the
197 sake of the whole community of users. You may or may not receive a
198 response; the maintainers will send one if that helps them find or
199 verify a fix. Most GNU maintainers are volunteers and all are
200 overworked; they don't have time to help individuals and still fix the
201 bugs and make the improvements that everyone wants. If you want help
202 for yourself in particular, you may have to hire someone. The GNU
203 project maintains a list of people providing such services. It is
204 distributed with GNU Emacs in file etc/SERVICE, and can be requested
205 from gnu@prep.ai.mit.edu.
206
207 Anything addressed to the implementors and maintainers of a GNU program
208 via a bug-* list, should NOT be sent to the corresponding info-* or
209 help-* list.
210
211 Please DON'T post your bug reports on the gnu.*.bug newsgroups! Mail
212 them to bug-*@prep instead! At first sight, it seems to make no
213 difference: anything sent to one will be propagated to the other; but:
214 - if you post on the newsgroup, the information about how to
215 reach you is lost in the message that goes on the mailing list. It
216 can be very important to know how to reach you, if there is anything
217 in the bug report that we don't understand;
218 - bug reports reach the GNU maintainers quickest when they are
219 sent to the bug-* mailing list submittal address;
220 - mail is much more reliable then netnews; and
221 - if the internet mailers can't get your bug report delivered,
222 they almost always send you an error message, so you can find another
223 way to get the bug report in. When netnews fails to get your message
224 delivered to the maintainers, you'll never know about it and the
225 maintainers will never see the bug report.
226
227 And please DON'T post your GNU bug reports to comp.* or other gnu.*
228 newsgroups, they never make it to the GNU maintainers at all. Please
229 mail them to bug-*@prep instead!
230
231 See section '* General Information about all lists'.
232
233 * info-gnu-request@prep.ai.mit.edu to subscribe to info-gnu
234 ** gnUSENET newsgroup: gnu.announce
235 ** Send announcements to: info-gnu@prep.ai.mit.edu
236
237 This list distributes progress reports on the GNU Project. It is also
238 used by the GNU Project to ask people for various kinds of help. It is
239 NOT for general discussion.
240
241 The list is filtered to remove items meant for info-gnu-request, that
242 can be answered by the moderator without bothering the list, or should
243 have been sent to another list.
244
245 See section '* General Information about info-* lists'.
246
247 * gnu-misc-discuss-request@prep.ai.mit.edu to subscribe to gnu-misc-discuss
248 ** gnUSENET newsgroup: gnu.misc.discuss
249 ** Send contributions to: gnu-misc-discuss@prep.ai.mit.edu
250
251 This list is for serious discussion of freed software, the GNU Project,
252 the GNU Manifesto, and their implications. It's THE place for
253 discussion that is not appropriate in the other GNU mailing lists and
254 gnUSENET newsgroups.
255
256 Flaming is out of place. Tit-for-tat is not welcome. Repetition
257 should not occur.
258
259 Good READING and writing are expected. Before posting, wait a while,
260 cool off, and think.
261
262 Don't use this group for complaints and bug reports about GNU software!
263 The maintainers don't read this group; they won't see your complaint.
264 Use the appropriate bug-reporting mailing list instead, so that people
265 who can do something about the problem will see it.
266
267 Don't trust pronouncements made on gnu-misc-discuss about what GNU is,
268 what FSF position is, what the GNU General Public License is, etc.,
269 unless they are made by someone you know is well connected with GNU and
270 are sure the message is not forged.
271
272 USENET and gnUSENET readers are expected to have read ALL the articles
273 in news.announce.newusers before posting. If news.announce.newusers is
274 empty at your site, wait (the articles are posted monthly), your posting
275 isn't that urgent! Readers on the Internet can anonymous FTP these
276 articles from host ftp.uu.net under directory ??
277
278 Someone from the Free Software Foundation will attempt to follow this
279 group as time and volume permits.
280
281 Remember, "GNUs Not Unix" and "gnUSENET is Not USENET". We have
282 higher standards!
283
284 Note that sending technical questions about specific GNU software to
285 gnu-misc-discuss is likely to be less useful than sending them to the
286 appropriate mailing list or gnUSENET newsgroup, since more technical
287 people read those.
288
289 * bug-gnu-sql-request@prep.ai.mit.edu to subscribe to bug-gnu-sql
290 ** gnUSENET newsgroup: NONE PLANNED
291 ** GNU-SQL BUG reports to: bug-gnu-sql@prep.ai.mit.edu
292
293 This list distributes, to the active maintainers of GNU's SQL (GNU's SQL
294 full scale database server), bug reports and fixes for, and suggestions
295 for improvements to GNU's SQL. User discussion of GNU's SQL also occurs
296 here.
297
298 There are no other GNU mailing lists or gnUSENET newsgroups for GNU's SQL.
299
300 See section '* General Information about bug-* lists and reporting
301 program bugs'.
302
303 * bug-guile-request@prep.ai.mit.edu to subscribe to bug-guile
304 ** gnUSENET newsgroup: NONE PLANNED
305 ** GUILE BUG reports to: bug-guile@prep.ai.mit.edu
306
307 This list distributes, to the active maintainers of GUILE (GNU's
308 Ubiquitous Extension Language), bug reports and fixes for, and suggestions for
309 improvements to GUILE. User discussion of GUILE also occurs here.
310
311 There are no other GNU mailing lists or gnUSENET newsgroups for GUILE .
312
313 See section '* General Information about bug-* lists and reporting
314 program bugs'.
315
316 * guile-sources-request@prep.ai.mit.edu to subscribe to guile-sources
317 ** gnUSENET newsgroup: NONE PLANNED
318 ** Guile source code to: guile-sources@prep.ai.mit.edu
319
320 This list will be for the posting, by their authors, of GUILE, Scheme,
321 and C sources and patches that improve Guile. Its contents will be
322 reviewed by the FSF for inclusion in future releases of GUILE.
323
324 Please do NOT discuss or request source code here. Use bug-guile for
325 those purposes. This allows the automatic archiving of sources posted
326 to this list.
327
328 Please do NOT post such sources to any other GNU mailing list (e.g
329 bug-guile) or gnUSENET newsgroups. It's up to each poster to decide
330 whether to cross-post to any non-gnUSENET newsgroup.
331
332 Please do NOT announce that you have posted source code to guile.sources
333 to any other GNU mailing list (e.g. bug-guile) or gnUSENET newsgroups.
334 People who want to keep up with sources will read this list. It's up to
335 each poster to decide whether to announce a guile.sources article in any
336 non-gnUSENET newsgroup (e.g. comp.emacs or comp.sources.d).
337
338 If source or patches that were previously posted or a simple fix is
339 requested in bug-guile, please mail it to the requester. Do NOT
340 repost it. If you also want something that is requested, send mail to
341 the requester asking him to forward it to you. This kind of traffic is
342 best handled by e-mail, not by a broadcast medium that reaches millions
343 of sites.
344
345 If the requested source is very long (>10k bytes) send mail offering to
346 send it. This prevents the requester from getting many redundant copies
347 and saves network bandwidth.
348
349 * bug-gnustep-request@prep.ai.mit.edu to subscribe to bug-gnustep
350 ** gnUSENET newsgroup: gnu.gnustep.bug
351 ** Gnustep bug reports to: bug-gnustep@prep.ai.mit.edu
352 ** FAQ-URL: none known
353 ** FAQ-Archive-name: none known
354 ** FAQ-Posting-frequency: none known
355
356 This list distributes bug reports for, fixes for bugs in, and
357 suggestions for improvements in GNUstep to its active developers.
358
359 Subscribers to bug-gnustep get all info-gnustep messages.
360
361 See section '* General Information about bug-* lists and reporting
362 program bugs'.
363
364 * help-gnustep-request@prep.ai.mit.edu to subscribe to help-gnustep
365 ** gnUSENET newsgroup: gnu.gnustep.help
366 ** Send contributions to: help-gnustep@prep.ai.mit.edu
367 ** FAQ-URL: none known
368 ** FAQ-Archive-name: none known
369 ** FAQ-Posting-frequency: none known
370
371 This list is the place for users and installers of the GNUstep to ask
372 for help. Please send bug reports to bug-gnustep@prep.ai.mit.edu
373 instead of posting them here.
374
375 See section '* General Information about help-* lists'.
376
377 * discuss-gnustep-request@prep.ai.mit.edu to subscribe to discuss-gnustep
378 ** gnUSENET newsgroup: gnu.gnustep.discuss
379 ** Send contributions to: discuss-gnustep@prep.ai.mit.edu
380 ** FAQ-URL: none known
381 ** FAQ-Archive-name: none known
382 ** FAQ-Posting-frequency: none known
383
384 This list is the place for GNUstep users and developers to discuss
385 GNUstep. Please send bug reports to bug-gnustep@prep.ai.mit.edu
386 instead of posting them here.
387
388 See section '* General Information about discuss-* lists'.
389
390 * info-gnustep-request@prep.ai.mit.edu to subscribe to info-gnustep
391 ** gnUSENET newsgroup: gnu.gnustep.announce
392 ** Send announcements to: info-gnustep@prep.ai.mit.edu
393 ** FAQ-URL: none known
394 ** FAQ-Archive-name: none known
395 ** FAQ-Posting-frequency: none known
396
397 This list distributes announcements and progress reports on GNUstep.
398 It is NOT for general discussion; please use discuss-gnustep for that.
399
400 The list is filtered to remove items meant for info-gnustep-request, that
401 can be answered by the moderator without bothering the list, or should
402 have been sent to another list.
403
404 Do not report GNUstep bugs to info-gnustep, help-gnustep, or
405 discuss-gnustep, mail them to bug-gnustep@prep.ai.mit.edu instead.
406
407 See section '* General Information about info-* lists'.
408
409 * bug-hurd-request@prep.ai.mit.edu to subscribe to bug-hurd
410 ** gnUSENET newsgroup: gnu.hurd.bug
411 ** Hurd bug reports to: bug-hurd@prep.ai.mit.edu
412
413 This list distributes bug reports for, fixes for bugs in, and
414 suggestions for improvements in the GNU Hurd to its active developers.
415
416 No info-gnu-hurd list is planned. Announcements about the GNU Hurd will
417 be made to the list info-gnu@prep.ai.mit.edu (see above).
418
419 See section '* General Information about bug-* lists and reporting
420 program bugs'.
421
422 * help-hurd-request@prep.ai.mit.edu to subscribe to help-hurd
423 ** gnUSENET newsgroup: gnu.hurd.help
424 ** Send contributions to: help-hurd@prep.ai.mit.edu
425
426 This list is the place for users and installers of the GNU Hurd to ask
427 for help.
428
429 No info-gnu-hurd list is planned. Announcements about the GNU Hurd will
430 be made to the list info-gnu@prep.ai.mit.edu (see above).
431
432 See section '* General Information about help-* lists'.
433
434 * hurd-ann-request@prep.ai.mit.edu IS NOW DEFUNCT
435 ** gnUSENET newsgroup: NEVER EXISTED
436 ** DEAD address: hurd-ann@prep.ai.mit.edu
437
438 This list is dead. Announcements about the GNU Hurd will be made to the
439 list info-gnu@prep.ai.mit.edu (see above).
440
441 * bug-gnu-emacs-request@prep.ai.mit.edu to subscribe to bug-gnu-emacs
442 ** gnUSENET newsgroup: gnu.emacs.bug
443 ** Gnu Emacs bug reports to: bug-gnu-emacs@prep.ai.mit.edu
444
445 This list distributes, to the active maintainers of GNU Emacs, bug
446 reports and fixes for, and suggestions for improvements in GNU Emacs.
447
448 Send bugs in the GNU Emacs Lisp reference manual to:
449 lisp-manual-bugs@prep.ai.mit.edu
450
451 lisp-manual-bugs is neither a mailing list nor a gnUSENET newsgroup.
452 It's just a bug-reporting address.
453
454 Subscribers to bug-gnu-emacs get all info-gnu-emacs messages.
455
456 See section '* General Information about bug-* lists and reporting
457 program bugs'.
458
459 * gnu-emacs-sources-request@prep.ai.mit.edu to subscribe to gnu-emacs-sources
460 ** gnUSENET newsgroup: gnu.emacs.sources
461 ** Gnu Emacs source code to: gnu-emacs-sources@prep.ai.mit.edu
462
463 This list/newsgroup will be for the posting, by their authors, of Emacs
464 Lisp and C sources and patches that improve GNU Emacs. Its contents
465 will be reviewed by the FSF for inclusion in future releases of GNU
466 Emacs.
467
468 Please do NOT discuss or request source code here. Use
469 help-gnu-emacs/gnu.emacs.help for those purposes. This allows the
470 automatic archiving of sources posted to this list/newsgroup.
471
472 Please do NOT post such sources to any other GNU mailing list (e.g
473 help-gnu-emacs) or gnUSENET newsgroups (e.g. gnu.emacs.help). It's up
474 to each poster to decide whether to cross-post to any non-gnUSENET
475 newsgroup (e.g. comp.emacs or vmsnet.sources).
476
477 Please do NOT announce that you have posted source code to
478 gnu.emacs.sources to any other GNU mailing list (e.g. help-gnu-emacs) or
479 gnUSENET newsgroups (e.g. gnu.emacs.help). People who want to keep up
480 with sources will read this list/newsgroup. It's up to each poster to
481 decide whether to announce a gnu.emacs.sources article in any
482 non-gnUSENET newsgroup (e.g. comp.emacs or comp.sources.d).
483
484 If source or patches that were previously posted or a simple fix is
485 requested in help-gnu-emacs, please mail it to the requester. Do NOT
486 repost it. If you also want something that is requested, send mail to
487 the requester asking him to forward it to you. This kind of traffic is
488 best handled by e-mail, not by a broadcast medium that reaches millions
489 of sites.
490
491 If the requested source is very long (>10k bytes) send mail offering to
492 send it. This prevents the requester from getting many redundant copies
493 and saves network bandwidth.
494
495 * help-gnu-emacs-request@prep.ai.mit.edu to subscribe to help-gnu-emacs
496 ** gnUSENET newsgroup: gnu.emacs.help (and one-way into comp.emacs)
497 ** Send contributions to: help-gnu-emacs@prep.ai.mit.edu
498
499 This list is the place for users and installers of GNU Emacs to ask for
500 help. Please send bug reports to bug-gnu-emacs instead of posting them
501 here.
502
503 Since help-gnu-emacs is a very large list, send it only those items that
504 are seriously important to many people.
505
506 If source or patches that were previously posted or a simple fix is
507 requested in help-gnu-emacs, please mail it to the requester. Do NOT
508 repost it. If you also want something that is requested, send mail to
509 the requester asking him to forward it to you. This kind of traffic is
510 best handled by e-mail, not a broadcast medium that reaches millions of
511 sites.
512
513 This list is also gated one way to USENET's newsgroup comp.emacs (once
514 known as net.emacs). This one-way gating is done for users whose sites
515 get comp.emacs, but not gnu.emacs.help. Users at non-USENET sites may
516 receive all articles from comp.emacs by making their request to:
517 unix-emacs-request@bbn.com
518
519 If Emacs crashes, or if you build Emacs following the standard procedure
520 on a system which Emacs is supposed to work on (see etc/MACHINES) and it
521 does not work at all, or if an editing command does not behave as it is
522 documented to behave, this is a bug. Don't send bug reports to
523 help-gnu-emacs (gnu.emacs.help) or post them to comp.emacs; mail them to
524 bug-gnu-emacs@prep.ai.mit.edu instead.
525
526 See section '* General Information about help-* lists'.
527
528 * info-gnu-emacs-request@prep.ai.mit.edu to subscribe to info-gnu-emacs
529 ** gnUSENET newsgroup: gnu.emacs.announce (and one-way into comp.emacs)
530 ** Send announcements to: info-gnu-emacs@prep.ai.mit.edu
531
532 This list distributes announcements and progress reports on GNU Emacs.
533 It is NOT for general discussion; please use help-gnu-emacs for that.
534
535 The list is filtered to remove items meant for info-gnu-emacs-request,
536 that can be answered by the moderator without bothering the list, or
537 should have been sent to another list.
538
539 info-gnu-emacs is also gated one way to USENET's newsgroup comp.emacs
540 (once known as net.emacs). This one-way gating is done for users whose
541 sites get comp.emacs, but not gnu.emacs.announce. Users at non-USENET
542 sites may receive all articles from comp.emacs by making their request
543 to: unix-emacs-request@bbn.com
544
545 Do not report GNU Emacs bugs to info-gnu-emacs or comp.emacs, instead
546 mail them to bug-gnu-emacs@prep.ai.mit.edu.
547
548 See section '* General Information about info-* lists'.
549
550 * vms-gnu-emacs-request@prep.ai.mit.edu to subscribe
551 ** gnUSENET newsgroup: gnu.emacs.vms
552 ** Send contributions to: vms-gnu-emacs@prep.ai.mit.edu
553
554 This list was a working group who did the initial port of GNU Emacs to
555 the VMS operating system. It still discusses problems and solutions to
556 the VMS port and the distribution of it.
557
558 * bug-bash-request@prep.ai.mit.edu to subscribe to bug-bash
559 ** gnUSENET newsgroup: gnu.bash.bug
560 ** BASH bug reports to: bug-bash@prep.ai.mit.edu
561
562 This list distributes, to the active maintainers of BASH (the Bourne
563 Again SHell), bug reports and fixes for, and suggestions for
564 improvements in BASH. User discussion of BASH also occurs here.
565
566 Always report the version number of the operating system, hardware, and
567 bash (flag -version on startup or check the variable $BASH_VERSION in a
568 running bash).
569
570 There are no other GNU mailing lists or gnUSENET newsgroups for BASH.
571
572 See section '* General Information about bug-* lists and reporting
573 program bugs'.
574
575 * bug-gdb-request@prep.ai.mit.edu to subscribe to bug-gdb
576 ** gnUSENET newsgroup: gnu.gdb.bug
577 ** GDB bug reports to: bug-gdb@prep.ai.mit.edu
578
579 This list distributes, to the active maintainers of GDB (Gnu's
580 DeBugger), bug reports and fixes for, and suggestions for improvements
581 in GDB.
582
583 There are no other GNU mailing lists or gnUSENET newsgroups for GDB.
584
585 See section '* General Information about bug-* lists and reporting
586 program bugs'.
587
588 * bug-octave-request@che.utexas.edu to subscribe to bug-octave
589 ** gnUSENET newsgroup: NONE PLANNED
590 ** Octave bug reports to: bug-octave@che.utexas.edu
591
592 This list distributes, to the active maintainers of Octave (a system
593 for numerical computations), bug reports and fixes for, and
594 suggestions for improvements to Octave.
595
596 The help-octave mailing list is for user discussion of Octave.
597
598 See section '* General Information about bug-* lists and reporting
599 program bugs'.
600
601
602 * help-octave-request@che.utexas.edu to subscribe to help-octave
603 ** gnUSENET newsgroup: NONE PLANNED
604 ** Send contributions to: help-octave@che.utexas.edu
605
606 This list is the place for users and installers of Octave to ask for
607 help. Please send bug reports to bug-octave instead of posting them
608 here.
609
610 If Octave crashes, or if you build Octave following the standard
611 procedure on a system on which Octave is supposed to work on and it
612 does not work at all, or if a command does not behave as it is
613 documented to behave, this is a bug. Don't send bug reports to
614 help-octave; mail them to bug-octave@che.utexas.edu instead.
615
616 See section '* General Information about help-* lists'.
617
618 * bug-gcc-request@prep.ai.mit.edu to subscribe to bug-gcc
619 ** gnUSENET newsgroup: gnu.gcc.bug
620 ** GCC bug reports to: bug-gcc@prep.ai.mit.edu
621
622 This list distributes bug reports for, fixes for bugs in, and
623 suggestions for improvements in the GNU C Compiler to its active
624 developers.
625
626 Please don't send in a patch without a test case to illustrate the
627 problem the patch is supposed to fix. Sometimes the patches aren't
628 correct or aren't the best way to do the job, and without a test case
629 there is no way to debug an alternate fix.
630
631 The most convenient form of test case is a piece of cpp output that can
632 be passed directly to cc1. Preferably written in C, not C++ or
633 Objective C.
634
635 Subscribers to bug-gcc get all info-gcc messages.
636
637 See section '* General Information about bug-* lists and reporting
638 program bugs'.
639
640 * help-gcc-request@prep.ai.mit.edu to subscribe to help-gcc
641 ** gnUSENET newsgroup: gnu.gcc.help
642 ** Send contributions to: help-gcc@prep.ai.mit.edu
643
644 This list is the place for users and installers of the GNU C Compiler to
645 ask for help.
646
647 If gcc crashes, or if you build gcc following the standard procedure on
648 a system which gcc is supposed to work on (see config.sub) and it does
649 not work at all, or if an command line option does not behave as it is
650 documented to behave, this is a bug. Don't send bug reports to help-gcc
651 (gnu.gcc.help); mail them to bug-gcc@prep.ai.mit.edu instead.
652
653 See section '* General Information about help-* lists'.
654
655 * info-gcc-request@prep.ai.mit.edu to subscribe to info-gcc
656 ** gnUSENET newsgroup: gnu.gcc.announce
657 ** Send announcements to: info-gcc@prep.ai.mit.edu
658
659 This list distributes announcements and progress reports on the GNU C
660 Compiler. It is NOT for general discussion; please use help-gcc for
661 that.
662
663 The list is filtered to remove items meant for info-gcc-request, that
664 can be answered by the moderator without bothering the list, or should
665 have been sent to another list.
666
667 See section '* General Information about info-* lists'.
668
669 * bug-gnu960-request@ichips.intel.com to subscribe to bug-gnu960
670 ** gnUSENET newsgroup: NONE PLANNED
671 ** Intel 960 Port bug reports to: bug-gnu960@ichips.intel.com
672
673 This list distributes bug reports for, fixes for bugs in, and
674 suggestions for improvements in Intel's port of GNU software to the
675 Intel 960 microprocessor.
676
677 You can also fax to: GNU/960 - 1-503-696-4930.
678
679 There are no other GNU mailing lists or gnUSENET newsgroups for Intel's
680 port of GNU software to the Intel 960 microprocessor.
681
682 See section '* General Information about bug-* lists and reporting
683 program bugs'.
684
685 * bug-glibc-request@prep.ai.mit.edu to subscribe to bug-glibc
686 ** gnUSENET newsgroup: gnu.glibc.bug
687 ** GNU C Library bug reports to: bug-glibc@prep.ai.mit.edu
688
689 This list distributes, to the active maintainers of glibc (GNU's C
690 library), bug reports and fixes for, and suggestions for improvements in
691 glibc. User discussion of glibc also occurs here.
692
693 Announcements of new releases of glibc are made on both info-gcc and
694 bug-glibc.
695
696 There are no other GNU mailing lists or gnUSENET newsgroups for the GNU
697 C Library.
698
699 See section '* General Information about bug-* lists and reporting
700 program bugs'.
701
702 * bug-g++-request@prep.ai.mit.edu to subscribe to bug-g++
703 ** gnUSENET newsgroup: gnu.g++.bug
704 ** G++ bug reports to: bug-g++@prep.ai.mit.edu
705
706 This list distributes bug reports for, fixes for bugs in, and
707 suggestions for improvements in the GNU C++ Compiler to its active
708 developers.
709
710 G++ uses the GNU C-Compiler back end. Active developers may wish to
711 subscribe to bug-gcc@prep.ai.mit.edu as well.
712
713 Subscribers to bug-g++ get all info-g++ messages.
714
715 See section '* General Information about bug-* lists and reporting
716 program bugs'.
717
718 * help-g++-request@prep.ai.mit.edu to subscribe to help-g++
719 ** gnUSENET newsgroup: gnu.g++.help (and one-way into comp.lang.c++)
720 ** Send contributions to: help-g++@prep.ai.mit.edu
721
722 This list is the place for users and installers of the GNU C++ Compiler
723 to ask for help. Please send bug reports to bug-g++@prep.ai.mit.edu
724 instead of posting them here.
725
726 help-g++ is also gated one way to USENET's newsgroup comp.lang.c++.
727 This one-way gating is done for users whose sites get comp.lang.c++, but
728 not gnu.g++.help.
729
730 See section '* General Information about help-* lists'.
731
732 * info-g++-request@prep.ai.mit.edu to subscribe to info-g++
733 ** gnUSENET newsgroup: gnu.g++.announce (and one-way into comp.lang.c++)
734 ** Send announcements to: info-g++@prep.ai.mit.edu
735
736 This list distributes announcements and progress reports on the GNU C++
737 Compiler. It is NOT for general discussion; please use help-g++ for
738 that.
739
740 The list is filtered to remove items meant for info-g++-request, that
741 can be answered by the moderator without bothering the list, or should
742 have been sent to another list.
743
744 It is also gated one way to USENET's newsgroup comp.lang.c++. This
745 one-way gating is done for users whose sites get comp.lang.c++, but not
746 gnu.g++.announce.
747
748 Do not report g++ bugs to info-g++ or comp.lang.c++, mail them to
749 bug-g++@prep.ai.mit.edu instead.
750
751 See section '* General Information about info-* lists'.
752
753 * bug-lib-g++-request@prep.ai.mit.edu to subscribe to bug-lib-g++
754 ** gnUSENET newsgroup: gnu.g++.lib.bug
755 ** lib-g++ bug reports to: bug-lib-g++@prep.ai.mit.edu
756
757 This list distributes, to the active maintainers of libg++ (GNU's
758 library for C++), bug reports and fixes for, and suggestions for
759 improvements in lib-g++. User discussion of libg++ also occurs here.
760
761 Announcements of new releases of libg++ are made on both info-g++ and
762 bug-lib-g++.
763
764 There are no other GNU mailing lists or gnUSENET newsgroups for GNU's
765 G++ Library.
766
767 See section '* General Information about bug-* lists and reporting
768 program bugs'.
769
770 * info-gnu-fortran-request@prep.ai.mit.edu to subscribe to info-gnu-fortran
771 ** gnUSENET newsgroup: NONE YET
772 ** Send announcements to: info-gnu-fortran@prep.ai.mit.edu
773
774 This list is for progress reports about the GNU Fortran compiler. In
775 the future it will also be used for release notices.
776
777 The list is filtered to remove items meant for info-gnu-fortran-request,
778 that can be answered by the moderator without bothering the list, or
779 should have been sent to another list.
780
781 People on the Internet can get a current status report by fingering the
782 address fortran@gnu.ai.mit.edu.
783
784 See section '* General Information about info-* lists'.
785
786 There are no other GNU mailing lists or gnUSENET newsgroups for GNU
787 Fortran (yet).
788
789 * bug-oleo-request@prep.ai.mit.edu to subscribe to bug-oleo
790 ** gnUSENET newsgroup: NONE PLANNED
791 ** Oleo bug reports to: bug-oleo@prep.ai.mit.edu
792
793 This list distributes, to the active maintainers of Oleo (the GNU
794 spreadsheet), bug reports and fixes for, and suggestions for
795 improvements to Oleo. User discussion of Oleo also occurs here.
796
797 There are no other GNU mailing lists or gnUSENET newsgroups for Oleo .
798
799 See section '* General Information about bug-* lists and reporting
800 program bugs'.
801
802 * bug-gmp-request@prep.ai.mit.edu to subscribe to bug-gmp
803 ** gnUSENET newsgroup: NONE PLANNED
804 ** gmp bug reports to: bug-gmp@prep.ai.mit.edu
805
806 This list distributes, to the active maintainers of gmp (the GNU
807 Multiple Precision Library), bug reports and fixes for, and suggestions
808 for improvements to gmp. User discussion of gmp also occurs here.
809
810 There are no other GNU mailing lists or gnUSENET newsgroups for gmp .
811
812 See section '* General Information about bug-* lists and reporting
813 program bugs'.
814
815 * bug-pine-request@prep.ai.mit.edu to subscribe to bug-pine
816 ** gnUSENET newsgroup: NONE PLANNED
817 ** pine bug reports to: bug-pine@prep.ai.mit.edu
818
819 This list distributes, to the active maintainers of pine (the GNU
820 version of the pine mail reader), bug reports and fixes for, and suggestions
821 for improvements to pine. User discussion of pine also occurs here.
822
823 There are no other GNU mailing lists or gnUSENET newsgroups for pine .
824
825 See section '* General Information about bug-* lists and reporting
826 program bugs'.
827
828 * bug-cfengine-request@prep.ai.mit.edu to subscribe to bug-cfengine
829 ** gnUSENET newsgroup: gnu.cfengine.bug
830 ** cfengine bug reports to: bug-cfengine@prep.ai.mit.edu
831
832 This list distributes, to the active maintainers of cfengine (configure
833 BSD and System-5-like operating systems attached to a TCP/IP network),
834 bug reports and fixes for, and suggestions for improvements to cfengine.
835 User discussion of cfengine also occurs here.
836
837 See section '* General Information about bug-* lists and reporting
838 program bugs'.
839
840 * help-cfengine-request@prep.ai.mit.edu to subscribe to help-cfengine
841 ** gnUSENET newsgroup: gnu.cfengine.help
842 ** Send contributions to: help-cfengine@prep.ai.mit.edu
843
844 This list is the place for users and installers of cfengine to ask for
845 help. Please send bug reports to bug-cfengine instead of posting them
846 here.
847
848 This list is also used for announcements about cfengine and related
849 programs, and small but important patches. Announcements of cfengine
850 releases are also made to info-gnu@prep.ai.mit.edu (see above)
851
852 Since help-cfengine is a large list, send it only those items that
853 are seriously important to many people.
854
855 If source or patches that were previously posted or a simple fix is
856 requested in help-cfengine, please mail it to the requester. Do NOT
857 repost it. If you also want something that is requested, send mail to
858 the requester asking him to forward it to you. This kind of traffic is
859 best handled by e-mail, not a broadcast medium that reaches millions of
860 sites.
861
862 See section '* General Information about help-* lists'.
863 Also see section '* General Information about info-* lists'.
864
865 * bug-gnu-smalltalk-request@prep.ai.mit.edu to subscribe to bug-gnu-smalltalk
866 ** gnUSENET newsgroup: gnu.smalltalk.bug
867 ** GNU Smalltalk bug reports to: bug-gnu-smalltalk@prep.ai.mit.edu
868
869 GNU Smalltalk is the GNU project implementation of the Smalltalk language.
870
871 This list distributes, to the active maintainers of GNU Smalltalk, bug
872 reports and fixes for, and suggestions for improvements to GNU
873 Smalltalk. User discussion of GNU Smalltalk also occurs here.
874
875 For now, new releases of GNU Smalltalk will also be announced on this list.
876
877 There are no other GNU mailing lists or gnUSENET newsgroups for GNU
878 Smalltalk.
879
880 See section '* General Information about bug-* lists and reporting
881 program bugs'.
882
883 * st-next-request@laplace.eng.sun.com to subscribe to st-next
884 ** gnUSENET newsgroup: NONE PLANNED
885 ** Send contributions to: st-next@laplace.eng.sun.com
886
887 For people interested in working on GNU Smalltalk on the NeXT.
888
889 * bug-groff-request@prep.ai.mit.edu to subscribe to bug-groff
890 ** gnUSENET newsgroup: gnu.groff.bug
891 ** GNU groff bug reports to: bug-groff@prep.ai.mit.edu
892
893 groff is the GNU project implementation, in C++, of the traditional Unix
894 document formatting tools.
895
896 This list distributes, to the active maintainers of groff, bug reports
897 and fixes for, and suggestions for improvements to groff (and it
898 component programs). User discussion of groff also occurs here.
899
900 For now, new releases of groff will also be announced on this list.
901
902 There are no other GNU mailing lists or gnUSENET newsgroups for groff.
903
904 See section '* General Information about bug-* lists and reporting
905 program bugs'.
906
907 * bug-ghostscript-request@prep.ai.mit.edu to subscribe to bug-ghostscript
908 ** gnUSENET newsgroup: gnu.ghostscript.bug
909 ** Ghostscript bug reports to: bug-ghostscript@prep.ai.mit.edu
910
911 Ghostscript is the GNU project implementation of a language and graphics
912 library with a remarkable similarity to PostScript.
913
914 This list distributes, to the active maintainers of Ghostscript, bug
915 reports and fixes for, and suggestions for improvements in Ghostscript.
916
917 For now, new releases of Ghostscript will also be announced on this list.
918
919 There are no other GNU mailing lists or gnUSENET newsgroups for
920 Ghostscript.
921
922 See section '* General Information about bug-* lists and reporting
923 program bugs'.
924
925 * bug-gnu-utils-request@prep.ai.mit.edu to subscribe to bug-gnu-utils
926 ** gnUSENET newsgroup: gnu.utils.bug
927 ** GNU Utilities bug reports to: bug-gnu-utils@prep.ai.mit.edu
928
929 This list distributes, to the active maintainers of these programs, bug
930 reports and fixes for, and suggestions for improvements in GNU programs
931 not covered by other bug-* mailing lists/gnu.*.bug newsgroups.
932
933 See section '* General Information about bug-* lists and reporting
934 program bugs'.
935
936 * help-gnu-utils-request@prep.ai.mit.edu to subscribe to help-gnu-utils
937 ** gnUSENET newsgroup: gnu.utils.help
938 ** Send contributions to: help-gnu-utils@prep.ai.mit.edu
939
940 This list is the place for users and installers of GNU programs not
941 covered by other GNU mailing lists/gnu.* newsgroups to ask for help.
942
943 Don't send bug reports to help-gnu-utils (gnu.utils.help); mail them to
944 bug-gnu-utils@prep.ai.mit.edu instead.
945
946 See section '* General Information about help-* lists'.
947
948 * info-gnu-utils-request@prep.ai.mit.edu IS NOW DEFUNCT
949 ** a gnUSENET newsgroup bever existed
950 ** DEAD address: info-gnu-utils@prep.ai.mit.edu
951
952 This list is dead. Announcements about GNU Utilities will be made to the
953 list info-gnu@prep.ai.mit.edu (see above).
954
955 * info-cvs-request@prep.ai.mit.edu to subscribe to info-cvs.
956 ** USENET newsgroup: (none)
957 ** CVS discussions/questions to: info-cvs@prep.ai.mit.edu
958
959 This list is for discussion and dissemination of information about
960 CVS. Please check the FAQ before posting questions, however.
961
962 * bug-cvs-request@prep.ai.mit.edu to subscribe to bug-cvs.
963 ** USENET newsgroup: (none)
964 ** CVS bug reports to: bug-cvs@prep.ai.mit.edu
965
966 This list distributes bug reports, fixes, and suggestions for
967 improvements to the maintainers of CVS.
968
969 * bug-fortran-mode-request@erl.mit.edu to subscribe to bug-fortran-mode
970 ** USENET newsgroup: (none)
971 ** Fortran mode bug reports to: bug-fortran-mode@erl.mit.edu
972
973 This list collects bug reports, fixes for bugs, and suggestions for
974 improvements in GNU Emacs's Fortran mode (a major mode to support
975 editing Fortran source code).
976
977 It is the place to report Fortran mode bugs by all users of Fortran
978 mode.
979
980 Always report the version number Fortran mode reports on startup as well
981 as the version of Emacs.
982
983 There is no info-fortran-mode list. There are no USENET gateways to
984 bug-fortran-mode at this time.
985
986 * info-gnus-request@flab.fujitsu.co.jp to subscribe
987 ** gnUSENET newsgroup: NONE YET
988 ** Send contributions to: info-gnus@flab.fujitsu.co.jp
989
990 The list is intended to exchange useful information about GNUS, such as
991 bug reports, useful hooks, and extensions of GNUS. GNUS is an NNTP-base
992 network news reader for GNU Emacs (which also works with a news spool).
993 English and Japanese are the official languages of the list. GNUS is
994 quite different than gnews.
995
996 * info-gnus-english-request@prep.ai.mit.edu to subscribe
997 ** gnUSENET newsgroup: gnu.emacs.gnus
998 ** Send contributions to: info-gnus-english@prep.ai.mit.edu
999
1000 The list has the same charter as info-gnus. The difference is that
1001 English is the only official language of the list.
1002
1003 info-gnus-english/gnu.emacs.gnus is forward to info-gnus, but NOT
1004 vice-versa.
1005
1006 * info-gnews-request@ics.uci.edu to subscribe to info-gnews
1007 ** gnUSENET newsgroup: gnu.emacs.gnews
1008 ** Send contributions to: info-gnews@ics.uci.edu
1009
1010 This newsgroup is intended to exchange useful information about gnews,
1011 such as bug reports, useful hooks, and extensions of gnews. gnews is an
1012 NNTP-base network news reader for GNU Emacs (which also works a news
1013 spool). It is quite different than GNUS.
1014
1015 * gnu-emacs-ada-request@grebyn.com to subscribe to gnu-emacs-ada
1016 ** gnUSENET newsgroup: NONE PLANNED
1017 ** Gnu Emacs Ada support bug reports to: gnu-emacs-ada@grebyn.com
1018
1019 This list distributes bug reports for, fixes for bugs in, and
1020 suggestions for improvements in GNU Emacs' editing support of the Ada
1021 programming language.
1022
1023 There are no other GNU mailing lists or gnUSENET newsgroups for GNU
1024 Emacs' editing support of Ada.
1025
1026 See section '* General Information about bug-* lists and reporting
1027 program bugs'.
1028
1029 * bug-vm-request@uunet.uu.net to subscribe to bug-vm
1030 ** gnUSENET newsgroup: gnu.emacs.vm.bug
1031 ** VM mail reader bug reports to: bug-vm@uunet.uu.net
1032
1033 This list discusses bugs in View Mail mode for GNU Emacs, with an
1034 emphasis on beta and prerelease versions.
1035
1036 Always report the version number of VM you are using, as well as the
1037 version of Emacs you're running. If you believe it is significant,
1038 report the operating system used and the hardware.
1039
1040 Subscribers to bug-vm get all info-vm messages.
1041
1042 * info-vm-request@uunet.uu.net to subscribe to info-vm
1043 ** gnUSENET newsgroup: gnu.emacs.vm.info
1044 ** Send contributions to: info-vm@uunet.uu.net
1045
1046 This list discusses the View Mail mode for GNU Emacs, an alternative to
1047 rmail mode.
1048
1049 * supercite-request@warsaw.nlm.nih.gov to subscribe to supercite
1050 ** gnUSENET newsgroup: NONE PLANNED
1051 ** Send articles to: supercite@warsaw.nlm.nih.gov
1052 *** UUCP: ..!uunet!warsaw.nlm.nih.gov!supercite-request
1053
1054 The supercite mailing list covers issues related to the advanced
1055 mail/news citation package called Supercite for GNU Emacs.
1056
1057 * auc-tex-request@iesd.auc.dk to subscribe
1058 ** USENET newsgroup: NONE YET
1059 ** Send contributions to: auc-tex@iesd.auc.dk
1060
1061 The list is intended to exchange information about AUC TeX, such as
1062 bug reports, request for help, and information on current
1063 developments. AUC TeX is a much enhanced LaTeX mode for GNU Emacs.
1064
1065 The list is unmoderated.
1066
1067 * bug-gnu-chess-request@prep.ai.mit.edu to subscribe to bug-gnu-chess
1068 ** gnUSENET newsgroup: gnu.chess.bug
1069 ** GNU Chess bug reports to: bug-gnu-chess@prep.ai.mit.edu
1070
1071 This list directly accesses the GNU Chess developer's group. If you
1072 have a *BUG* to report about the program, which can also include a
1073 feature enhancement request, please send it to this list.
1074
1075 Subscribers to bug-gnu-chess get all info-gnu-chess messages.
1076
1077 See section '* General Information about bug-* lists and reporting
1078 program bugs'.
1079
1080 * help-gnu-chess-request@prep.ai.mit.edu IS NOW DEFUNCT
1081 ** gnUSENET newsgroup: NONE PLANNED
1082 ** DEAD address: help-gnu-chess@prep.ai.mit.edu
1083
1084 This list is dead. Use info-gnu-chess@prep.ai.mit.edu/gnu.chess instead.
1085
1086 * info-gnu-chess-request@prep.ai.mit.edu to subscribe to info-gnu-chess
1087 ** gnUSENET newsgroup: gnu.chess
1088 ** Send contributions to: info-gnu-chess@prep.ai.mit.edu
1089 ** FAQ-URL: http://www.research.digital.com/SRC/personal/Tim_Mann/chess.html
1090 ** FAQ-Archive-name: games/chess/gnu-faq
1091 ** FAQ-Posting-frequency: monthly
1092
1093 This list is the place for users and installers of GNU Chess to ask for
1094 help. This list is also used for games played by people or other
1095 entities against the program, and other generalized non-bug,
1096 non-enhancement data. Please send bug reports to bug-gnu-chess instead
1097 of posting them here.
1098
1099 This list is also used for announcements about GNU Chess and related
1100 programs, and small but important patches. Announcements of GNU Chess
1101 releases are also made to info-gnu@prep.ai.mit.edu (see above)
1102
1103 Since info-gnu-chess is a large list, send it only those items that
1104 are seriously important to many people.
1105
1106 If source or patches that were previously posted or a simple fix is
1107 requested in info-gnu-chess, please mail it to the requester. Do NOT
1108 repost it. If you also want something that is requested, send mail to
1109 the requester asking him to forward it to you. This kind of traffic is
1110 best handled by e-mail, not a broadcast medium that reaches millions of
1111 sites.
1112
1113 See section '* General Information about help-* lists'.
1114 Also see section '* General Information about info-* lists'.
1115
1116 * bug-gnu-shogi-request@prep.ai.mit.edu to subscribe to bug-gnu-shogi
1117 ** gnUSENET newsgroup: NONE PLANNED
1118 ** GNU Shogi bug reports to: bug-gnu-shogi@prep.ai.mit.edu
1119
1120 This list directly accesses the GNU Shogi developer's group. If you
1121 have a *BUG* to report about the program, which can also include a
1122 feature enhancement request, please send it to this list.
1123
1124 Subscribers to bug-gnu-shogi get all info-gnu-shogi messages.
1125
1126 See section '* General Information about bug-* lists and reporting
1127 program bugs'.
1128
1129 Shogi is a game something like chess. There are several different types
1130 of pieces, a board that is 9 by 9 squares, and the modification that a
1131 captured piece can be reintroduced on the board by the capturing player
1132 (and used). Due to this last difference from Western chess, a Shogi
1133 game never simplifies.
1134
1135 * help-gnu-shogi-request@prep.ai.mit.edu IS NOW DEFUNCT
1136 ** gnUSENET newsgroup: NONE PLANNED
1137 ** DEAD address: help-gnu-shogi@prep.ai.mit.edu
1138
1139 This list is dead.
1140
1141 * info-gnu-shogi-request@prep.ai.mit.edu to subscribe to info-gnu-shogi
1142 ** gnUSENET newsgroup: NONE PLANNED
1143 ** Send contributions to: info-gnu-shogi@prep.ai.mit.edu
1144
1145 This list is the place for users and installers of GNU Shogi to ask for
1146 help. This list is also used for games played by people or other
1147 entities against the program, and other generalized non-bug,
1148 non-enhancement data. Please send bug reports to bug-gnu-shogi instead
1149 of posting them here.
1150
1151 This list is also used for announcements about GNU Shogi and related
1152 programs, and small but important patches. Announcements of GNU Shogi
1153 releases are also made to info-gnu@prep.ai.mit.edu (see above)
1154
1155 Since info-gnu-shogi is a large list, send it only those items that
1156 are seriously important to many people.
1157
1158 If source or patches that were previously posted or a simple fix is
1159 requested in info-gnu-shogi, please mail it to the requester. Do NOT
1160 repost it. If you also want something that is requested, send mail to
1161 the requester asking him to forward it to you. This kind of traffic is
1162 best handled by e-mail, not a broadcast medium that reaches millions of
1163 sites.
1164
1165 See section '* General Information about help-* lists'.
1166 Also see section '* General Information about info-* lists'.
1167
1168 * gnu-manual-request@a.cs.uiuc.edu IS NOW DEFUNCT
1169 ** DEAD: Gnusenet newsgroup: gnu.emacs.lisp.manual
1170 ** DEAD address: gnu-manual@a.cs.uiuc.edu
1171 *** DEAD UUCP address: ..!uunet!uiucdcs!gnu-manual-request
1172
1173 This list and newsgroup is dead. It was a working group whose
1174 volunteers wrote, proofread and commented on the developing GNU Emacs
1175 Lisp programmers manual.
1176
1177 Send bugs in the GNU Emacs Lisp reference manual to:
1178 lisp-manual-bugs@prep.ai.mit.edu
1179
1180 lisp-manual-bugs is neither a mailing list nor a gnUSENET newsgroup.
1181 It's just a bug-reporting address.
1182
1183 * no mailing list request
1184 ** gnUSENET newsgroup: gnu.gnusenet.config
1185 ** no mailing list
1186
1187 This newsgroup has nothing to do with GNU software, especially its
1188 configuration. It exists to distribute information about the
1189 administration and configuration of gnUSENET: the gnu.all alternative
1190 USENET hierarchy that carry the GNU mailing lists.
1191
1192 Administrators of gnUSENET hosts receiving the gnu.all newsgroups are
1193 welcome to ask questions here or via e-mail of gnu@prep.ai.mit.edu.
1194
1195 * no mailing list request
1196 ** gnUSENET newsgroup: gnu.gnusenet.test
1197 ** no mailing list
1198
1199 This newsgroup has nothing to do with GNU software, especially its
1200 testing. It exists to allow test messages to be made in gnUSENET: the
1201 gnu.all alternative USENET hierarchy that carry the GNU mailing lists.
1202
1203 Local variables:
1204 mode: outline
1205 fill-column: 72
1206 End: