If you would like to join the discussion and receive all messages sent to these mailing lists, please send a short note to -help-octave-request@bevo.che.wisc.edu (to join help-octave) or -bug-octave-request@bevo.che.wisc.edu (to join bug-octave), or -octave-sources-request@bevo.che.wisc.edu (to join octave-sources). +help-request@octave.org (to join help-octave) or +bug-request@octave.org (to join bug-octave), or +sources-request@octave.org (to join octave-sources).
@@ -67,7 +67,7 @@
-Back to the Octave home page. +Back to the Octave home page.
diff -r b6ff3a0d3d17 -r b2ce28713791 WWW/readme.html --- a/WWW/readme.html Mon Sep 27 13:50:01 2004 +0000 +++ b/WWW/readme.html Fri Oct 01 18:12:11 2004 +0000 @@ -348,7 +348,7 @@ currently no complete documentation of the C++ class libraries or the support for dynamic linking and user-defined data types. If you notice ommissions or inconsistencies, please report them as bugs to -bug-octave@bevo.che.wisc.edu. Specific suggestions for ways to +bug@@octave.org. Specific suggestions for ways to improve Octave and its documentation are always welcome.
diff -r b6ff3a0d3d17 -r b2ce28713791 doc/faq/Octave-FAQ.texi --- a/doc/faq/Octave-FAQ.texi Mon Sep 27 13:50:01 2004 +0000 +++ b/doc/faq/Octave-FAQ.texi Fri Oct 01 18:12:11 2004 +0000 @@ -26,11 +26,11 @@ Some information in this FAQ was written for earlier versions of Octave and may now be obsolete. -I'm looking for new questions (@emph{with} answers), better answers, -or both. Please send suggestions to bug-octave@@bevo.che.wisc.edu. -If you have general questions about Octave, or need help for something -that is not covered by the Octave manual or the FAQ, please use the -help-octave@@bevo.che.wisc.edu mailing list. +I'm looking for new questions (@emph{with} answers), better answers, or +both. Please send suggestions to bug@@octave.org. If you have general +questions about Octave, or need help for something that is not covered +by the Octave manual or the FAQ, please use the help@@octave.org mailing +list. This FAQ is intended to supplement, not replace, the Octave manual. Before posting a question to the help-octave mailing list, you should @@ -466,7 +466,7 @@ The Octave manual is intended to be a complete reference for Octave, but it is not a finished document. If you have problems using it, or find that some topic is not adequately explained, indexed, or -cross-referenced, please send a bug report to bug-octave@@bevo.che.wisc.edu. +cross-referenced, please send a bug report to bug@@octave.org. Because the Octave manual is written using Texinfo, the complete text of the Octave manual is also available on line using the GNU Info system @@ -529,7 +529,7 @@ Binaries for several popular systems are also available. If you would like help out by making binaries available for other systems, please -contact bug-octave@@bevo.che.wisc.edu. +contact bug@@octave.org. A list of user-visible changes since the last release is available in the file @file{NEWS}. The file @file{ChangeLog} in the source @@ -551,7 +551,7 @@ (using the Cygwin tools from Red Hat). It should be possible to make Octave work on other systems as well. If you are interested in porting Octave to other systems, please contact -bug-octave@@bevo.che.wisc.edu. +bug@@octave.org. @node latest versions @section What is the latest version of Octave @@ -609,7 +609,7 @@ would be nice to make it possible to compile Octave with other C++ compilers, but the maintainers do not have sufficient time to devote to this. If you are interested in working to make Octave portable to other -compilers, please contact bug-octave@@bevo.che.wisc.edu. +compilers, please contact bug@@octave.org. @node Common problems @chapter Common problems @@ -641,7 +641,7 @@ The mailing list @example -help-octave@@bevo.che.wisc.edu +help@@octave.org @end example @noindent @@ -654,8 +654,8 @@ @example @group -help-octave-request@@bevo.che.wisc.edu - ^^^^^^^ +help-request@@octave.org + ^^^^^^^ @end group @end example @@ -693,11 +693,10 @@ @cindex Mailing lists, bug-octave If for some reason you cannot use Octave's @code{bug_report} function, -mail your bug report to "bug-octave@@bevo.che.wisc.edu". Your message -needs to include enough information to allow the maintainers of Octave -to fix the bug. Please read the section on bugs and bug reports in the -Octave manual for a list of things that should be included in every bug -report. +mail your bug report to "bug@@octave.org". Your message needs to +include enough information to allow the maintainers of Octave to fix the +bug. Please read the section on bugs and bug reports in the Octave +manual for a list of things that should be included in every bug report. @node MATLAB compatibility @chapter Porting programs from @sc{Matlab} to Octave @@ -760,7 +759,7 @@ The third category of differences is (hopefully) shrinking. If you find a difference between Octave behavior and @sc{Matlab}, then you should send a description of this difference (with code illustrating the difference, -if possible) to bug-octave@@bevo.che.wisc.edu. +if possible) to bug@@octave.org. An archive of old postings to the Octave mailing lists is maintained on ftp.che.wisc.edu in the directory @file{/pub/octave/MAILING-LISTS}. diff -r b6ff3a0d3d17 -r b2ce28713791 doc/interpreter/bugs.txi --- a/doc/interpreter/bugs.txi Mon Sep 27 13:50:01 2004 +0000 +++ b/doc/interpreter/bugs.txi Fri Oct 01 18:12:11 2004 +0000 @@ -235,7 +235,7 @@ for you. If for some reason you cannot use Octave's @code{bug_report} function, -send bug reports for Octave to @email{bug-octave@@bevo.che.wisc.edu}. +send bug reports for Octave to @email{bug@@octave.org}. @strong{Do not send bug reports to @samp{help-octave}}. Most users of Octave do not want to receive bug reports. Those that do have asked to @@ -461,15 +461,15 @@ @appendixsec How To Get Help with Octave @cindex help, where to find -The mailing list @email{help-octave@@bevo.che.wisc.edu} exists for the -discussion of matters related to using and installing Octave. If would -like to join the discussion, please send a short note to -@email{help-octave@strong{-request}@@bevo.che.wisc.edu}. +The mailing list @email{help@@octave.org} exists for the discussion of +matters related to using and installing Octave. If would like to join +the discussion, please send a short note to +@email{help@strong{-request}@@octave.org}. @strong{Please do not} send requests to be added or removed from the mailing list, or other administrative trivia to the list itself. If you think you have found a bug in the installation procedure, however, you should send a complete bug report for the problem to -@email{bug-octave@@bevo.che.wisc.edu}. @xref{Bug Reporting}, for +@email{bug@@octave.org}. @xref{Bug Reporting}, for information that will help you to submit a useful report. diff -r b6ff3a0d3d17 -r b2ce28713791 doc/interpreter/image.txi --- a/doc/interpreter/image.txi Mon Sep 27 13:50:01 2004 +0000 +++ b/doc/interpreter/image.txi Fri Oct 01 18:12:11 2004 +0000 @@ -15,7 +15,7 @@ colormap). Contributions of robust, well-written functions to read other image formats are welcome. If you can provide them, or would like to improve Octave's image processing capabilities in other ways, please -contact @email{bug-octave@@bevo.che.wisc.edu}. +contact @email{bug@@octave.org}. @DOCSTRING(colormap) diff -r b6ff3a0d3d17 -r b2ce28713791 doc/interpreter/octave-bug.1 --- a/doc/interpreter/octave-bug.1 Mon Sep 27 13:50:01 2004 +0000 +++ b/doc/interpreter/octave-bug.1 Fri Oct 01 18:12:11 2004 +0000 @@ -46,7 +46,7 @@ Please read the `Bugs' chapter in the Octave manual to find out how to submit a bug report that will enable the Octave maintainers to fix the problem. If you are unable to use the bug_report command, send your message to the -bug-octave mailing list, bug-octave@bevo.che.wisc.edu. +bug-octave mailing list, bug@octave.org. .SH OPTIONS .TP .BI -s\ subject diff -r b6ff3a0d3d17 -r b2ce28713791 doc/interpreter/octave.1 --- a/doc/interpreter/octave.1 Mon Sep 27 13:50:01 2004 +0000 +++ b/doc/interpreter/octave.1 Fri Oct 01 18:12:11 2004 +0000 @@ -67,7 +67,7 @@ .PP If you are unable to use the bug_report command, send your message to the -.B bug-octave@bevo.che.wisc.edu +.B bug@octave.org mailing list by some other means. Please read the `Bugs' chapter in the Octave manual to find out how to submit a bug report that will enable the Octave maintainers to fix the problem. diff -r b6ff3a0d3d17 -r b2ce28713791 doc/interpreter/signal.txi --- a/doc/interpreter/signal.txi Mon Sep 27 13:50:01 2004 +0000 +++ b/doc/interpreter/signal.txi Fri Oct 01 18:12:11 2004 +0000 @@ -7,7 +7,7 @@ I hope that someday Octave will include more signal processing functions. If you would like to help improve Octave in this area, -please contact @email{bug-octave@@bevo.che.wisc.edu}. +please contact @email{bug@@octave.org}. @DOCSTRING(detrend) diff -r b6ff3a0d3d17 -r b2ce28713791 doc/interpreter/stats.txi --- a/doc/interpreter/stats.txi Mon Sep 27 13:50:01 2004 +0000 +++ b/doc/interpreter/stats.txi Fri Oct 01 18:12:11 2004 +0000 @@ -7,7 +7,7 @@ I hope that someday Octave will include more statistics functions. If you would like to help improve Octave in this area, please contact -@email{bug-octave@@bevo.che.wisc.edu}. +@email{bug@@octave.org}. @menu * Basic Statistical Functions:: diff -r b6ff3a0d3d17 -r b2ce28713791 doc/interpreter/stmt.txi --- a/doc/interpreter/stmt.txi Mon Sep 27 13:50:01 2004 +0000 +++ b/doc/interpreter/stmt.txi Fri Oct 01 18:12:11 2004 +0000 @@ -206,9 +206,9 @@ be considered experimental, and details of the implementation may change slightly in future versions of Octave. If you have comments or would like to share your experiences in trying to use this new command in real -programs, please send them to -@email{octave-maintainers@@bevo.che.wisc.edu}. (But if you think you've -found a bug, please report it to @email{bug-octave@@bevo.che.wisc.edu}. +programs, please send them to @email{maintainers@@octave.org}. (But if +you think you've found a bug, please report it to +@email{bug@@octave.org}. The general form of the @code{switch} statement is diff -r b6ff3a0d3d17 -r b2ce28713791 doc/interpreter/tips.txi --- a/doc/interpreter/tips.txi Mon Sep 27 13:50:01 2004 +0000 +++ b/doc/interpreter/tips.txi Fri Oct 01 18:12:11 2004 +0000 @@ -37,7 +37,7 @@ If you write a function that you think ought to be added to Octave under a certain name, such as @code{fiddle_matrix}, don't call it by that name in your program. Call it @code{mylib_fiddle_matrix} in your program, -and send mail to @email{bug-octave@@bevo.che.wisc.edu} suggesting that it +and send mail to @email{maintainers@@octave.org} suggesting that it be added to Octave. If and when it is, the name can be changed easily enough. diff -r b6ff3a0d3d17 -r b2ce28713791 emacs/octave-mod.el --- a/emacs/octave-mod.el Mon Sep 27 13:50:01 2004 +0000 +++ b/emacs/octave-mod.el Fri Oct 01 18:12:11 2004 +0000 @@ -436,7 +436,7 @@ is why you need this mode!). The latest released version of Octave is always available via anonymous -ftp from bevo.che.wisc.edu in the directory `/pub/octave'. Complete +ftp from ftp.octave.org in the directory `/pub/octave'. Complete source and binaries for several popular systems are available. Type \\[list-abbrevs] to display the built-in abbrevs for Octave keywords. diff -r b6ff3a0d3d17 -r b2ce28713791 octave-bug.in --- a/octave-bug.in Mon Sep 27 13:50:01 2004 +0000 +++ b/octave-bug.in Fri Oct 01 18:12:11 2004 +0000 @@ -99,7 +99,7 @@ ss_p=`echo $VERSION | grep "^ss-"` if test -n "$ss_p"; then - BUGADDR="octave-maintainers@bevo.che.wisc.edu" + BUGADDR="maintainers@octave.org" else pretest_p=`echo $VERSION \ | $SED 's,.*\.\([0-9]*\).*,\1,' \ @@ -107,9 +107,9 @@ | grep '[0-9]'` if test -n "$pretest_p" && test "$pretest_p" -ge 90; then - BUGADDR="octave-maintainers@bevo.che.wisc.edu" + BUGADDR="maintainers@octave.org" else - BUGADDR="bug-octave@bevo.che.wisc.edu" + BUGADDR="bug@octave.org" fi fi diff -r b6ff3a0d3d17 -r b2ce28713791 scripts/plot/__plt2vm__.m --- a/scripts/plot/__plt2vm__.m Mon Sep 27 13:50:01 2004 +0000 +++ b/scripts/plot/__plt2vm__.m Fri Oct 01 18:12:11 2004 +0000 @@ -70,6 +70,7 @@ k++; endif endfor + cmd eval (cmd); else error ("__plt2vm__: arguments must be a matrices"); diff -r b6ff3a0d3d17 -r b2ce28713791 src/file-io.cc --- a/src/file-io.cc Mon Sep 27 13:50:01 2004 +0000 +++ b/src/file-io.cc Fri Oct 01 18:12:11 2004 +0000 @@ -31,7 +31,7 @@ // sync_system (now merged with system) // async_system (now merged with system) -// Completely rewritten by John W. Eaton