Update links to MAP repository.
M contributing/documents.php +2 -2
@@ 12,9 12,9 @@ 
 
 <h1>MAP document authoring tutorial</h1>
 
-<p>On this page I’ll try to explain some guidelines for authoring a document for the MAP. Check <a href="https://bitbucket.org/grauw/map/src/default/contributing/documents.php">the source on Mercurial</a> to see how everything is done in this (and other) pages’ source code.</p>
+<p>On this page I’ll try to explain some guidelines for authoring a document for the MAP. Check <a href="https://hg.sr.ht/~grauw/map/browse/@/contributing/documents.php">the source on Mercurial</a> to see how everything is done in this (and other) pages’ source code.</p>
 
-<p>You can go ahead and get the source code from the <a href="https://bitbucket.org/grauw/map">MAP Mercurial repository</a>. From there, You can start a new article or add a new resource, or modify an existing one. But keep in mind the social aspect of editing documents, that every article is made and thus ‘owned’ by someone. So although corrections are fine, you probably shouldn’t push significant modifications onto the server without consulting with the author first. Also, if you want to make changes to the style sheet or site structure, drop me (Grauw) a line first :).</p>
+<p>You can go ahead and get the source code from the <a href="https://hg.sr.ht/~grauw/map">MAP Mercurial repository</a>. From there, You can start a new article or add a new resource, or modify an existing one. But keep in mind the social aspect of editing documents, that every article is made and thus ‘owned’ by someone. So although corrections are fine, you probably shouldn’t push significant modifications onto the server without consulting with the author first. Also, if you want to make changes to the style sheet or site structure, drop me (Grauw) a line first :).</p>
 
 <p>If you have push rights to the server, keep in mind that everything you push will be live immediately. Generally speaking, it’s also always useful if someone reviews your changes before they are pushed to the server. Of course, this review can also happen after things are pushed, but because we use Mercurial, if you are unsure about whether something is correct or using the right tags or correctly spelled or whatever, you can easily draft some changes and send them to someone else for review.</p>
 

          
M contributing/index.php +1 -1
@@ 24,7 24,7 @@ a certain subject, or digitize some docu
 yourself, we’d really appreciate it. Submitting changes to the MAP’s source code
 usually expedites the process of getting things online :).</p>
 
-<p>The <a href="https://bitbucket.org/grauw/map">MAP source code</a> is stored
+<p>The <a href="https://hg.sr.ht/~grauw/map">MAP source code</a> is stored
 in a <a href="http://www.selenic.com/mercurial/">Mercurial</a> repository. There
 is <a href="/contributing/repository.php">a tutorial</a> explaining how to get
 the sources and start making changes.</p>

          
M contributing/repository.php +3 -3
@@ 12,7 12,7 @@ 
 
 <p>The MSX Assembly Page source code is stored in a Mercurial revision control repository, which you can find here:</p>
 
-<p><a href="https://bitbucket.org/grauw/map">https://bitbucket.org/grauw/map</a></p>
+<p><a href="https://hg.sr.ht/~grauw/map">https://hg.sr.ht/~grauw/map</a></p>
 
 <p>Below you will find short instructions on how to work with Mercurial.</p>
 

          
@@ 26,7 26,7 @@ 
 
 <p>You start by cloning the main repository on your local system:</p>
 
-<pre>hg clone https://bitbucket.org/grauw/map</pre>
+<pre>hg clone https://hg.sr.ht/~grauw/map</pre>
 
 <p>Now you can start making changes. Every time you make a unit of related changes, you can commit them into your local repository:</p>
 

          
@@ 46,7 46,7 @@ 
 
 <p>Once your changes are ready for publication, you can push all the changes that you committed locally into the main repository, and they will automatically appear on the website. Note that in order to push, you need to use HTTPS. You can configure a <a href="http://www.selenic.com/mercurial/wiki/index.cgi/TipsAndTricks#head-903d2da677af8b40172345b98072b4b2826bad22">default push location</a> in Mercurial so that it will remember it.</p>
 
-<pre>hg push https://bitbucket.org/grauw/map</pre>
+<pre>hg push ssh://hg@hg.sr.ht/~grauw/map</pre>
 
 <p>In order to be able to push changes directly into the repository you need push rights, so if you do not have those then instead you can send your changes to the MAP by email using an ‘email-bundle’. You can do this easily from TortoiseHg, to use it from the command-line you need to first enable the <a href="http://www.selenic.com/mercurial/wiki/index.cgi/PatchbombExtension">Patchbomb extension</a> that is bundled with Mercurial.</p>
 

          
M index.php +1 -1
@@ 48,7 48,7 @@ linking to us is always allowed. For mor
 
 <ul>
   <li><a href="/disclaimer.php">Disclaimer</a></li>
-  <li><a href="https://bitbucket.org/grauw/map/commits/all">Changelog</a></li>
+  <li><a href="https://hg.sr.ht/~grauw/glass/log">Changelog</a></li>
   <li><a href="/updates-old.php">Old updates</a></li>
 </ul>
 

          
M updates-old.php +1 -1
@@ 99,7 99,7 @@ routine, thanks to Ricardo Bittencourt.<
 <p><em>2009-03-09</em><br />
 The MSX Assembly Page’s address has changed to
 <a href="http://map.grauw.nl/">http://map.grauw.nl/</a>. Source is now
-accessible in a <a href="https://bitbucket.org/grauw/map">public repository</a>, and
+accessible in a <a href="https://hg.sr.ht/~grauw/map">public repository</a>, and
 introducing a <a href="/contributing/">Contributing</a> section.</p>
 
 <p><em>2007-06-29</em><br />