Mercurial > octave-nkf

diff doc/interpreter/contrib.txi @ 15497:c49d891eb263 stable

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Update broken or inconsistent project and wiki urls * README, doc/interpreter/contrib.txi, etc/HACKING, etc/README.MacOS, etc/README.MinGW, etc/README.devel: Update urls to use the octave.org domain. * doc/faq/OctaveFAQ.texi, scripts/miscellaneous/info.m: Replace broken links to the manual and help mailing list. * doc/faq/OctaveFAQ.texi, etc/PROJECTS, etc/README.MacOS: Update wiki urls to short naming scheme. * doc/interpreter/contrib.txi, scripts/help/unimplemented.m: Make Octave-Forge project urls consistent. * src/version.h.in: Update url to contribution page.
author Mike Miller <mtmiller@ieee.org>
date Mon, 08 Oct 2012 08:01:07 -0400
parents 87f06b9990bb
children 3ae8c1ee7365 cfbc726cb4c5
line wrap: on
line diff
--- a/doc/interpreter/contrib.txi	Mon Oct 01 17:18:49 2012 -0400
+++ b/doc/interpreter/contrib.txi	Mon Oct 08 08:01:07 2012 -0400
@@ -41,7 +41,7 @@
 development of Octave core, i.e., code that goes to Octave directly.
 You may consider developing and publishing a package instead; a great
 place for this is the allied Octave-Forge project
-(@url{http://octave.sf.net}).  Note that the Octave project is
+(@url{http://octave.sourceforge.net}).  Note that the Octave project is
 inherently more conservative and follows narrower rules.
 
 @node Building the Development Sources
@@ -67,7 +67,7 @@
 @item
 Check out a copy of the Octave sources:
 @example
-hg clone http://hg.savannah.gnu.org/hgweb/octave
+hg clone http://www.octave.org/hg/octave
 @end example
 
 @item