Commit 3769e3a8 authored by Takenobu Tani's avatar Takenobu Tani Committed by Marge Bot
Browse files

Update Wiki URLs to point to GitLab

This moves all URL references to Trac Wiki to their corresponding
GitLab counterparts.

This substitution is classified as follows:

1. Automated substitution using sed with Ben's mapping rule [1]
    Old: ghc.haskell.org/trac/ghc/wiki/XxxYyy...
    New: gitlab.haskell.org/ghc/ghc/wikis/xxx-yyy...

2. Manual substitution for URLs containing `#` index
    Old: ghc.haskell.org/trac/ghc/wiki/XxxYyy...#Zzz
    New: gitlab.haskell.org/ghc/ghc/wikis/xxx-yyy...#zzz

3. Manual substitution for strings starting with `Commentary`
    Old: Commentary/XxxYyy...
    New: commentary/xxx-yyy...

See also !539

[1]: https://gitlab.haskell.org/bgamari/gitlab-migration/blob/master/wiki-mapping.json
parent 8e07368f
# Questions about this file?
# See https://ghc.haskell.org/trac/ghc/wiki/ContinuousIntegration/Usage.
# See https://gitlab.haskell.org/ghc/ghc/wikis/continuous-integration/usage.
version: 2
......
......@@ -10,10 +10,10 @@ Please take a few moments to verify that your commits fulfill the following:
likely should add a [Note][notes] and cross-reference it from the relevant
places.
* [ ] add a [testcase to the
testsuite](https://ghc.haskell.org/trac/ghc/wiki/Building/RunningTests/Adding).
testsuite](https://gitlab.haskell.org/ghc/ghc/wikis/building/running-tests/adding).
If you have any questions don't hesitate to open your merge request and inquire
in a comment. If your patch isn't quite done yet please do add prefix your MR
title with `WIP:`.
[notes]: https://ghc.haskell.org/trac/ghc/wiki/Commentary/CodingStyle#Commentsinthesourcecode
[notes]: https://gitlab.haskell.org/ghc/ghc/wikis/commentary/coding-style#comments-in-the-source-code
......@@ -241,7 +241,7 @@ Peter Wortmann <Peter.Wortmann@googlemail.com> <peter@grayson-heigh
Peter Wortmann <Peter.Wortmann@googlemail.com> <scpmw@leeds.ac.uk>
Peter Wortmann <Peter.Wortmann@googlemail.com> scpmw@leeds.ac.uk <unknown>
Piyush P. Kurur <ppk@cse.iitk.ac.in>
Ralf Laemmel <softlang@uni-koblenz.de> ralf <unknown> # https://ghc.haskell.org/trac/ghc/wiki/TeamGHC
Ralf Laemmel <softlang@uni-koblenz.de> ralf <unknown> # https://gitlab.haskell.org/ghc/ghc/wikis/team-ghc
Ravi Nanavati <ravi@bluespec.com> # Commit 70c044.
Reiner Pope <reiner.pope@gmail.com> <reinerp@google.com>
Reuben Thomas <rrt@sc3d.org> rrt <unknown>
......@@ -293,7 +293,7 @@ Spencer Janssen <spencer@well-typed.com> <sjanssen@cse.unl.ed
Stephen Blackheath <stephen@blacksapphire.com> <docks.cattlemen.stephen@blacksapphire.com>
Stephen Blackheath <stephen@blacksapphire.com> <effusively.proffer.stephen@blacksapphire.com>
Stephen Blackheath <stephen@blacksapphire.com> <oversensitive.pastors.stephen@blacksapphire.com>
Sungwoo Park <gla@postech.ac.kr> gla <unknown> # https://ghc.haskell.org/trac/ghc/wiki/TeamGHC
Sungwoo Park <gla@postech.ac.kr> gla <unknown> # https://gitlab.haskell.org/ghc/ghc/wikis/team-ghc
Sven Panne <sven.panne@aedion.de> panne <unknown>
Sven Panne <sven.panne@aedion.de> sven.panne@aedion.de <unknown>
Sylvain Henry <hsyl20@gmail.com>
......
......@@ -88,12 +88,12 @@ Supported Platforms
The list of platforms we support, and the people responsible for them, is here:
https://ghc.haskell.org/trac/ghc/wiki/TeamGHC
https://gitlab.haskell.org/ghc/ghc/wikis/team-ghc
Ports to other platforms are possible with varying degrees of difficulty. The
Building Guide describes how to go about porting to a new platform:
https://ghc.haskell.org/trac/ghc/wiki/Building
https://gitlab.haskell.org/ghc/ghc/wikis/building
Developers
......
......@@ -17,7 +17,7 @@ From here, you can file bugs (or look them up,) use the wiki, view the
page, which has the high level overview of the build process and how
to get the source:
<http://ghc.haskell.org/trac/ghc/wiki/Building>
<https://gitlab.haskell.org/ghc/ghc/wikis/building>
Contributing patches to GHC in a hurry
======================================
......@@ -25,7 +25,7 @@ Contributing patches to GHC in a hurry
Make sure your system has the necessary tools to compile GHC. You can
find an overview here:
<http://ghc.haskell.org/trac/ghc/wiki/Building/Preparation>
<https://gitlab.haskell.org/ghc/ghc/wikis/building/preparation>
Next, clone the repository and all the associated libraries:
......@@ -64,9 +64,9 @@ Now, hack on your copy and rebuild (with `make`) as necessary.
Then start by making your commits however you want. When you're done, you can submit
a pull request on Github for small changes. For larger changes the patch needs to be
submitted to [Phabricator](https://phabricator.haskell.org/) for code review.
The GHC Wiki has a good summary for the [overall process](https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/FixingBugs)
The GHC Wiki has a good summary for the [overall process](https://gitlab.haskell.org/ghc/ghc/wikis/working-conventions/fixing-bugs)
as well as a guide on
[how to use Phabricator/arcanist](https://ghc.haskell.org/trac/ghc/wiki/Phabricator).
[how to use Phabricator/arcanist](https://gitlab.haskell.org/ghc/ghc/wikis/phabricator).
Useful links:
......@@ -75,22 +75,22 @@ Useful links:
An overview of things like using git, the release process, filing bugs
and more can be located here:
<http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions>
<https://gitlab.haskell.org/ghc/ghc/wikis/working-conventions>
You can find our coding conventions for the compiler and RTS here:
<http://ghc.haskell.org/trac/ghc/wiki/Commentary/CodingStyle>
<http://ghc.haskell.org/trac/ghc/wiki/Commentary/Rts/Conventions>
<https://gitlab.haskell.org/ghc/ghc/wikis/commentary/coding-style>
<https://gitlab.haskell.org/ghc/ghc/wikis/commentary/rts/conventions>
A high level overview of the bug tracker:
<http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/BugTracker>
<https://gitlab.haskell.org/ghc/ghc/wikis/working-conventions/bug-tracker>
If you're going to contribute regularly, **learning how to use the
build system is important** and will save you lots of time. You should
read over this page carefully:
<http://ghc.haskell.org/trac/ghc/wiki/Building/Using>
<https://gitlab.haskell.org/ghc/ghc/wikis/building/using>
How to communicate with us
==========================
......
......@@ -44,5 +44,5 @@ References
==========
[1] http://www.haskell.org/ghc/
[2] http://ghc.haskell.org/trac/ghc/wiki/Building/Preparation
[2] https://gitlab.haskell.org/ghc/ghc/wikis/building/preparation
[3] http://www.haskell.org/haddock/
......@@ -3,9 +3,9 @@ Quick `make` guide for GHC
For a "Getting Started" guide, see:
https://ghc.haskell.org/trac/ghc/wiki/Building/QuickStart
https://ghc.haskell.org/trac/ghc/wiki/Building/Using
https://ghc.haskell.org/trac/ghc/wiki/Building/StandardTargets
https://gitlab.haskell.org/ghc/ghc/wikis/building/quick-start
https://gitlab.haskell.org/ghc/ghc/wikis/building/using
https://gitlab.haskell.org/ghc/ghc/wikis/building/standard-targets
Common commands:
......
......@@ -5,8 +5,8 @@
# This file is part of the GHC build system.
#
# To understand how the build system works and how to modify it, see
# http://ghc.haskell.org/trac/ghc/wiki/Building/Architecture
# http://ghc.haskell.org/trac/ghc/wiki/Building/Modifying
# https://gitlab.haskell.org/ghc/ghc/wikis/building/architecture
# https://gitlab.haskell.org/ghc/ghc/wikis/building/modifying
#
# -----------------------------------------------------------------------------
......
......@@ -31,7 +31,7 @@ There are two ways to get a source tree:
Note: cloning GHC from Github requires a special setup. See [Getting a GHC
repository from Github][7].
*See the GHC team's working conventions regarding [how to contribute a patch to GHC](http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/FixingBugs).* First time contributors are encouraged to get started by just sending a Pull Request.
*See the GHC team's working conventions regarding [how to contribute a patch to GHC](https://gitlab.haskell.org/ghc/ghc/wikis/working-conventions/fixing-bugs).* First time contributors are encouraged to get started by just sending a Pull Request.
Building & Installing
......@@ -109,19 +109,19 @@ you to join!
[1]: http://www.haskell.org/ghc/ "www.haskell.org/ghc/"
[2]: http://ghc.haskell.org/trac/ghc "ghc.haskell.org/trac/ghc"
[3]: http://ghc.haskell.org/trac/ghc/wiki/Building
"ghc.haskell.org/trac/ghc/wiki/Building"
[3]: https://gitlab.haskell.org/ghc/ghc/wikis/building
"https://gitlab.haskell.org/ghc/ghc/wikis/building"
[4]: http://www.haskell.org/happy/ "www.haskell.org/happy/"
[5]: http://www.haskell.org/alex/ "www.haskell.org/alex/"
[6]: http://www.haskell.org/haddock/ "www.haskell.org/haddock/"
[7]: https://ghc.haskell.org/trac/ghc/wiki/Building/GettingTheSources#GettingaGHCrepositoryfromGitHub
"https://ghc.haskell.org/trac/ghc/wiki/Building/GettingTheSources#GettingaGHCrepositoryfromGitHub"
[8]: http://ghc.haskell.org/trac/ghc/wiki/Building/Preparation
"http://ghc.haskell.org/trac/ghc/wiki/Building/Preparation"
[7]: https://gitlab.haskell.org/ghc/ghc/wikis/building/getting-the-sources#cloning-from-github
"https://gitlab.haskell.org/ghc/ghc/wikis/building/getting-the-sources#cloning-from-github"
[8]: https://gitlab.haskell.org/ghc/ghc/wikis/building/preparation
"https://gitlab.haskell.org/ghc/ghc/wikis/building/preparation"
[9]: http://www.haskell.org/cabal/ "http://www.haskell.org/cabal/"
[10]: https://gitlab.haskell.org/ghc/ghc/issues
"https://gitlab.haskell.org/ghc/ghc/issues"
[11]: http://www.haskell.org/pipermail/glasgow-haskell-users/
"http://www.haskell.org/pipermail/glasgow-haskell-users/"
[12]: http://ghc.haskell.org/trac/ghc/wiki/TeamGHC
"http://ghc.haskell.org/trac/ghc/wiki/TeamGHC"
[12]: https://gitlab.haskell.org/ghc/ghc/wikis/team-ghc
"https://gitlab.haskell.org/ghc/ghc/wikis/team-ghc"
......@@ -905,7 +905,7 @@ dnl 2. Find happy in path
dnl 3. Check happy version
dnl
dnl If you increase the minimum version requirement, please also update:
dnl https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Tools
dnl https://gitlab.haskell.org/ghc/ghc/wikis/building/preparation/tools
dnl
AC_DEFUN([FPTOOLS_HAPPY],
[AC_PATH_PROG(HAPPY,[happy],)
......@@ -938,7 +938,7 @@ dnl 2. Find alex in path
dnl 3. Check alex version
dnl
dnl If you increase the minimum version requirement, please also update:
dnl https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Tools
dnl https://gitlab.haskell.org/ghc/ghc/wikis/building/preparation/tools
dnl
AC_DEFUN([FPTOOLS_ALEX],
[AC_PATH_PROG(ALEX,[alex],)
......
......@@ -5,8 +5,8 @@
# This file is part of the GHC build system.
#
# To understand how the build system works and how to modify it, see
# http://ghc.haskell.org/trac/ghc/wiki/Building/Architecture
# http://ghc.haskell.org/trac/ghc/wiki/Building/Modifying
# https://gitlab.haskell.org/ghc/ghc/wikis/building/architecture
# https://gitlab.haskell.org/ghc/ghc/wikis/building/modifying
#
# -----------------------------------------------------------------------------
......
......@@ -5,8 +5,8 @@
# This file is part of the GHC build system.
#
# To understand how the build system works and how to modify it, see
# http://ghc.haskell.org/trac/ghc/wiki/Building/Architecture
# http://ghc.haskell.org/trac/ghc/wiki/Building/Modifying
# https://gitlab.haskell.org/ghc/ghc/wikis/building/architecture
# https://gitlab.haskell.org/ghc/ghc/wikis/building/modifying
#
# -----------------------------------------------------------------------------
......
......@@ -53,8 +53,8 @@ def check_for_url_rewrites():
git clone --recursive git://git.haskell.org/ghc.git
For more information, see:
* https://ghc.haskell.org/trac/ghc/wiki/Newcomers or
* https://ghc.haskell.org/trac/ghc/wiki/Building/GettingTheSources#CloningfromGitHub
* https://gitlab.haskell.org/ghc/ghc/wikis/newcomers or
* https://gitlab.haskell.org/ghc/ghc/wikis/building/getting-the-sources#cloning-from-github
""")
def check_boot_packages():
......@@ -186,7 +186,7 @@ def check_build_mk():
than simply building it to use it.
For information on creating a mk/build.mk file, please see:
http://ghc.haskell.org/trac/ghc/wiki/Building/Using#Buildconfiguration
https://gitlab.haskell.org/ghc/ghc/wikis/building/using#build-configuration
"""))
check_for_url_rewrites()
......
......@@ -5,8 +5,8 @@
# This file is part of the GHC build system.
#
# To understand how the build system works and how to modify it, see
# http://ghc.haskell.org/trac/ghc/wiki/Building/Architecture
# http://ghc.haskell.org/trac/ghc/wiki/Building/Modifying
# https://gitlab.haskell.org/ghc/ghc/wikis/building/architecture
# https://gitlab.haskell.org/ghc/ghc/wikis/building/modifying
#
# -----------------------------------------------------------------------------
......
......@@ -1571,7 +1571,7 @@ It is only effective if the one-shot info survives as long as possible; in
particular it must make it into the interface in unfoldings. See Note [Preserve
OneShotInfo] in CoreTidy.
Also see https://ghc.haskell.org/trac/ghc/wiki/OneShot.
Also see https://gitlab.haskell.org/ghc/ghc/wikis/one-shot.
Note [magicDictId magic]
......
......@@ -177,7 +177,7 @@ import {-# SOURCE #-} Packages (componentIdString, improveUnitId, PackageConfigM
-- Unit IDs, installed package IDs, ABI hashes, package names,
-- versions, there are a *lot* of different identifiers for closely
-- related things. What do they all mean? Here's what. (See also
-- https://ghc.haskell.org/trac/ghc/wiki/Commentary/Packages/Concepts )
-- https://gitlab.haskell.org/ghc/ghc/wikis/commentary/packages/concepts )
--
-- THE IMPORTANT ONES
--
......
......@@ -1216,7 +1216,7 @@ bestImport iss
{- Note [Choosing the best import declaration]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When reporting unused import declarations we use the following rules.
(see [wiki:Commentary/Compiler/UnusedImports])
(see [wiki:commentary/compiler/unused-imports])
Say that an import-item is either
* an entire import-all decl (eg import Foo), or
......
......@@ -223,11 +223,11 @@ use `deriving' because we want {\em precise} control of ordering
--
-- As such, to get deterministic builds, the order of the allocated
-- @Uniques@ should not affect the final result.
-- see also wiki/DeterministicBuilds
-- see also wiki/deterministic-builds
--
-- Note [Unique Determinism and code generation]
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- The goal of the deterministic builds (wiki/DeterministicBuilds, #4012)
-- The goal of the deterministic builds (wiki/deterministic-builds, #4012)
-- is to get ABI compatible binaries given the same inputs and environment.
-- The motivation behind that is that if the ABI doesn't change the
-- binaries can be safely reused.
......
......@@ -760,7 +760,7 @@ hasCAF _ = False
-- -----------------------------------------------------------------------------
-- Does a CLabel need declaring before use or not?
--
-- See wiki:Commentary/Compiler/Backends/PprC#Prototypes
-- See wiki:commentary/compiler/backends/ppr-c#prototypes
needsCDecl :: CLabel -> Bool
-- False <=> it's pre-declared; don't bother
......
......@@ -8,7 +8,7 @@
--
-- Print Cmm as real C, for -fvia-C
--
-- See wiki:Commentary/Compiler/Backends/PprC
-- See wiki:commentary/compiler/backends/ppr-c
--
-- This is simpler than the old PprAbsC, because Cmm is "macro-expanded"
-- relative to the old AbstractC, and many oddities/decorations have
......@@ -240,7 +240,7 @@ pprStmt stmt =
cast_fn = parens (cCast (pprCFunType (char '*') cconv hresults hargs) fn)
-- See wiki:Commentary/Compiler/Backends/PprC#Prototypes
-- See wiki:commentary/compiler/backends/ppr-c#prototypes
fnCall =
case fn of
CmmLit (CmmLabel lbl)
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment