Mercurial > mxe-octave

changeset 2339:fe146de226fe

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Replace links into the web repository from hg.savannah.nongnu.org to github.com History links have been preserved, though.
author Volker Grabsch <vog@notjusthosting.com>
date Wed, 28 Mar 2012 16:20:17 +0200
parents ecc478b45d13
children e56341d7a2df
files doc/index.html
diffstat 1 files changed, 7 insertions(+), 7 deletions(-) [+]
line wrap: on
line diff
--- a/doc/index.html	Wed Mar 28 16:14:40 2012 +0200
+++ b/doc/index.html	Wed Mar 28 16:20:17 2012 +0200
@@ -461,7 +461,7 @@
 
     <p>
     You can also browse the
-    <a href="http://hg.savannah.nongnu.org/hgweb/mingw-cross-env">web repository</a>.
+    <a href="https://github.com/mxe/mxe">web repository</a>.
     </p>
 
     <p>
@@ -919,13 +919,13 @@
         For instance,
         when adding a GNU library,
         you should take a package like
-        <a href="http://hg.savannah.gnu.org/hgweb/mingw-cross-env/file/tip/src/gettext.mk">gettext.mk</a>
+        <a href="https://github.com/mxe/mxe/blob/master/src/gettext.mk">gettext.mk</a>
         or
-        <a href="http://hg.savannah.gnu.org/hgweb/mingw-cross-env/file/tip/src/libiconv.mk">libiconv.mk</a>
+        <a href="https://github.com/mxe/mxe/blob/master/src/libiconv.mk">libiconv.mk</a>
         as the base of your work.
         When using a SourceForge project,
         you could start with a copy of
-        <a href="http://hg.savannah.gnu.org/hgweb/mingw-cross-env/file/tip/src/xmlwrapp.mk">xmlwrapp.mk</a>.
+        <a href="https://github.com/mxe/mxe/blob/master/src/xmlwrapp.mk">xmlwrapp.mk</a>.
         And so on.
         </p>
     </li>
@@ -964,7 +964,7 @@
         <p>
         You might also have to provide a patch for it.
         In that case, have a look at other patches such as
-        <a href="http://hg.savannah.gnu.org/hgweb/mingw-cross-env/file/tip/src/sdl-2-fix-dinput.patch">sdl-2-fix-dinput.patch</a>.
+        <a href="https://github.com/mxe/mxe/blob/master/src/sdl-2-fix-dinput.patch">sdl-2-fix-dinput.patch</a>.
         In particular, each patch file should be named as:
         </p>
         <pre>PACKAGE-PATCHNUMBER-DESCRIPTION.patch</pre>
@@ -1015,7 +1015,7 @@
         depending on whether it is a C or C++ library.
         To get a clue,
         please have a look at existing test programs such as
-        <a href="http://hg.savannah.gnu.org/hgweb/mingw-cross-env/file/tip/src/sdl-test.c">sdl-test.c</a>.
+        <a href="https://github.com/mxe/mxe/blob/master/src/sdl-test.c">sdl-test.c</a>.
         </p>
 
         <p>
@@ -1023,7 +1023,7 @@
         you should build the test program in a generic way,
         using strict compiler flags.
         The last few lines of
-        <a href="http://hg.savannah.gnu.org/hgweb/mingw-cross-env/file/tip/src/sdl.mk">sdl.mk</a>
+        <a href="https://github.com/mxe/mxe/blob/master/src/sdl.mk">sdl.mk</a>
         will give you a clue.
         </p>
     </li>