[PATCH] doc: remove two surviving references to bitbucket.org

[Antonio Muci]

# HG changeset patch
# User Antonio Muci <a....@inwind.it>
# Date 1701042373 -3600
# Mon Nov 27 00:46:13 2023 +0100
# Branch stable
# Node ID ec924c5eb5c5d02b6f8ed70d564233ce6bf48f2b
# Parent 5f8dbdddc63f1e1bc12beb6a1000ddd184d8066d
doc: remove two surviving references to bitbucket.org

TortoiseHg moved to Heptapod circa 2020.

diff --git a/doc/source/intro.txt b/doc/source/intro.txt
--- a/doc/source/intro.txt
+++ b/doc/source/intro.txt
@@ -134,7 +134,7 @@ The most recent Linux packages can be fo

For Mac OS X, no packages are available but you can run thg and all the
dialogs via the source install method. For details, see
-`Mac OS X <https://bitbucket.org/tortoisehg/thg/wiki/developers/MacOSX>`_.
+`Mac OS X <https://foss.heptapod.net/mercurial/tortoisehg/thg/-/wikis/developers/MacOSX>`_.

.. note::

diff --git a/doc/source/settings.txt b/doc/source/settings.txt
--- a/doc/source/settings.txt
+++ b/doc/source/settings.txt
@@ -670,8 +670,8 @@ Issue Tracking
``{rev}`` :
replaced by the revision number.

- For example, in order to link to bitbucket commit pages you can set
- this to: ``https://bitbucket.org/tortoisehg/thg/commits/{node|short}``
+ For example, in order to link to heptapod commit pages you can set
+ this to: ``https://foss.heptapod.net/mercurial/tortoisehg/thg/-/commit/{node}``


.. module:: reviewboard.settings

[Yuya Nishihara]

On Mon, 27 Nov 2023 00:46:46 +0100, 'Antonio Muci' via TortoiseHg Developers wrote:
> # HG changeset patch
> # User Antonio Muci <a....@inwind.it>
> # Date 1701042373 -3600
> # Mon Nov 27 00:46:13 2023 +0100
> # Branch stable
> # Node ID ec924c5eb5c5d02b6f8ed70d564233ce6bf48f2b
> # Parent 5f8dbdddc63f1e1bc12beb6a1000ddd184d8066d
> doc: remove two surviving references to bitbucket.org

Queued for stable, thanks.

[Matt Harbison]

I'm not aware of any compat issues with 6.6, so I guess we might as well roll an RC.

[Yuya Nishihara]

On Tue, 28 Nov 2023 20:31:48 -0800 (PST), 'Matt Harbison' via TortoiseHg Developers wrote:
> I'm not aware of any compat issues with 6.6, so I guess we might as well
> roll an RC.

Ok, tagged 6.6rc0, thanks.