Commit bf703351 authored by Ben Boeckel's avatar Ben Boeckel
Browse files

doc: update gitlab links to include the `/-/` component

parent 979243b0
......@@ -2,6 +2,6 @@ Thanks for your interest in contributing to ParaView! The GitHub repository
is a mirror provided for convenience, but ParaView does not use GitHub pull
requests for contribution. Please see
https://gitlab.kitware.com/paraview/paraview/tree/master/CONTRIBUTING.md
https://gitlab.kitware.com/paraview/paraview/-/tree/master/CONTRIBUTING.md
for contribution instructions. GitHub OAuth may be used to sign in.
......@@ -370,7 +370,7 @@ IDI_ICON1 ICON \"${_paraview_client_APPLICATION_ICON}\"\n")
PRIVATE
"${CMAKE_CURRENT_SOURCE_DIR}"
"${CMAKE_CURRENT_BINARY_DIR}"
# https://gitlab.kitware.com/cmake/cmake/issues/18049
# https://gitlab.kitware.com/cmake/cmake/-/issues/18049
"$<TARGET_PROPERTY:VTK::vtksys,INTERFACE_INCLUDE_DIRECTORIES>")
target_link_libraries("${_paraview_client_NAME}"
PRIVATE
......
......@@ -161,7 +161,7 @@ and to provide support.
[ParaView Git README]: Documentation/dev/git/README.md
[developer instructions]: Documentation/dev/git/develop.md
[GitLab Access]: https://gitlab.kitware.com/users/sign_in
[Fork ParaView]: https://gitlab.kitware.com/paraview/paraview/forks/new
[Fork ParaView]: https://gitlab.kitware.com/paraview/paraview/-/forks/new
[use SSH instead of HTTPS]: Documentation/dev/git/download.md#use-ssh-instead-of-https
[download instructions]: Documentation/dev/git/download.md#clone
[developer setup script]: /Utilities/SetupForDevelopment.sh
......@@ -172,12 +172,12 @@ and to provide support.
[Create a Merge Request]: Documentation/dev/git/develop.md#create-a-merge-request
[Review a Merge Request]: Documentation/dev/git/develop.md#review-a-merge-request
[review]: Documentation/dev/git/develop.md#review-a-merge-request
[Issues]: https://gitlab.kitware.com/paraview/paraview/issues
[Merge Requests]: https://gitlab.kitware.com/paraview/paraview/merge_requests
[Labels]: https://gitlab.kitware.com/paraview/paraview/labels
[Milestones]: https://gitlab.kitware.com/paraview/paraview/milestones
[Issues]: https://gitlab.kitware.com/paraview/paraview/-/issues
[Merge Requests]: https://gitlab.kitware.com/paraview/paraview/-/merge_requests
[Labels]: https://gitlab.kitware.com/paraview/paraview/-/labels
[Milestones]: https://gitlab.kitware.com/paraview/paraview/-/milestones
[Wiki]: http://www.paraview.org/Wiki/ParaView
[ParaView Discourse]: https://discourse.paraview.org/
[Gitlab Markdown]: https://gitlab.kitware.com/help/markdown/markdown
[new issue]: https://gitlab.kitware.com/paraview/paraview/issues/new
[new issue]: https://gitlab.kitware.com/paraview/paraview/-/issues/new
[Labels Glossary]: Documentation/dev/git/labels.md
......@@ -47,7 +47,7 @@
</screenshots>
<launchable type="desktop-id">org.paraview.ParaView.desktop</launchable>
<url type="homepage">http://paraview.org/</url>
<url type="bugtracker">https://gitlab.kitware.com/paraview/paraview/issues</url>
<url type="bugtracker">https://gitlab.kitware.com/paraview/paraview/-/issues</url>
<url type="faq">https://www.paraview.org/Wiki/ParaView:FAQ</url>
<url type="help">https://www.paraview.org/documentation/</url>
<update_contact>paraview+paraview-support@discourse.paraview.org</update_contact>
......
......@@ -530,7 +530,7 @@ steps:
[ninja]: https://github.com/ninja-build/ninja/releases
[nvpipe]: https://github.com/NVIDIA/NvPipe
[openmpi]: https://www.open-mpi.org
[paraview-issues]: https://gitlab.kitware.com/paraview/paraview/issues
[paraview-issues]: https://gitlab.kitware.com/paraview/paraview/-/issues
[python]: https://python.org
[pythonwindows]: https://www.python.org/downloads/windows/
[qt-download]: https://download.qt.io/official_releases/qt
......
......@@ -17,7 +17,7 @@ Main Tasks
Other Tasks
-----------
* [Review Changes](https://gitlab.kitware.com/paraview/paraview/merge_requests) -
* [Review Changes](https://gitlab.kitware.com/paraview/paraview/-/merge_requests) -
ParaView GitLab Merge Requests
* [Learn Git](http://public.kitware.com/Wiki/Git/Resources) -
Third-party documentation
......
......@@ -45,7 +45,7 @@ Before you begin, perform initial setup:
"Subscribe to this project" on the right of ParaView.
[GitLab Access]: https://gitlab.kitware.com/users/sign_in
[Fork ParaView]: https://gitlab.kitware.com/paraview/paraview/forks/new
[Fork ParaView]: https://gitlab.kitware.com/paraview/paraview/-/forks/new
[developer setup script]: /Utilities/SetupForDevelopment.sh
Workflow
......@@ -155,7 +155,7 @@ cases, being your topic name with the issue number.
This is not necessary for branches which are "trivial" such as fixing
typos, updating test baselines, or are developer-oriented.
[vtk instructions]: https://gitlab.kitware.com/vtk/vtk/blob/master/Documentation/dev/git/data.md
[vtk instructions]: https://gitlab.kitware.com/vtk/vtk/-/blob/master/Documentation/dev/git/data.md
Share a Topic
-------------
......@@ -182,7 +182,7 @@ signed in for [GitLab Access][] and created your fork by visiting the main
Notes:
* If you are revising a previously pushed topic and have rewritten the
topic history, add `-f` or `--force` to overwrite the destination.
* If the topic adds data see [this note](https://gitlab.kitware.com/vtk/vtk/blob/master/Documentation/dev/git/data.md#push).
* If the topic adds data see [this note](https://gitlab.kitware.com/vtk/vtk/-/blob/master/Documentation/dev/git/data.md#push).
* The `gitlab-push` script also pushes the `master` branch to your
fork in GitLab to keep it in sync with the upstream `master`.
......@@ -200,7 +200,7 @@ left, and use the "**New Merge Request**" button in the upper right to
reach the URL printed at the end of the [previous step](#share-a-topic).
It should be of the form:
https://gitlab.kitware.com/<username>/paraview/merge_requests/new
https://gitlab.kitware.com/<username>/paraview/-/merge_requests/new
Follow these steps:
......@@ -501,4 +501,4 @@ been approved and merged into VTK, then:
3. Follow the merge process documented earlier.
[VTK's development workflow]: https://gitlab.kitware.com/vtk/vtk/tree/master/Documentation/dev/git
[VTK's development workflow]: https://gitlab.kitware.com/vtk/vtk/-/tree/master/Documentation/dev/git
......@@ -77,6 +77,6 @@ at a time.
| `workflow:active-developement` | x | | added to an open issue that is under development |
| `workflow:customer-review` | x | | added to a closed issue that is ready for review by the customer/reporter |
[Labels]: https://gitlab.kitware.com/paraview/paraview/labels
[Issues]: https://gitlab.kitware.com/paraview/paraview/issues
[Merge Requests]: https://gitlab.kitware.com/paraview/paraview/merge_requests
[Labels]: https://gitlab.kitware.com/paraview/paraview/-/labels
[Issues]: https://gitlab.kitware.com/paraview/paraview/-/issues
[Merge Requests]: https://gitlab.kitware.com/paraview/paraview/-/merge_requests
......@@ -2,7 +2,7 @@ ParaView 5.5.0 Release Notes
============================
The full list of issues addressed by this release is available
[here](https://gitlab.kitware.com/paraview/paraview/milestones/7). Major changes
[here](https://gitlab.kitware.com/paraview/paraview/-/milestones/7). Major changes
made since ParaView 5.4.1 include the following:
# Rendering Enhancements
......
......@@ -21,5 +21,5 @@ appending time-varying data.
* The SDK packaging for Linux has been fixed.
The list of issues addressed by this release are available
[here](https://gitlab.kitware.com/paraview/paraview/milestones/11#tab-issues),
and merge requests included in this release are [here](https://gitlab.kitware.com/paraview/paraview/milestones/11#tab-merge-requests).
[here](https://gitlab.kitware.com/paraview/paraview/-/milestones/11#tab-issues),
and merge requests included in this release are [here](https://gitlab.kitware.com/paraview/paraview/-/milestones/11#tab-merge-requests).
......@@ -2,7 +2,7 @@ ParaView 5.6.0 Release Notes
============================
Major changes made since ParaView 5.5.2 are listed in this document. The full list of issues addressed by this release is available
[here](https://gitlab.kitware.com/paraview/paraview/milestones/8).
[here](https://gitlab.kitware.com/paraview/paraview/-/milestones/8).
# General Notes
......@@ -160,7 +160,7 @@ pvts, pvtr, pvtk, ply, stl
The name of the series file must follow the format \<filename\>.\<format\>.series,
e.g., `images.vti.series`. More information about the content of the file can be
found [here](https://gitlab.kitware.com/paraview/paraview/blob/v5.5.0/Documentation/release/ParaView-5.5.0.md).
found [here](https://gitlab.kitware.com/paraview/paraview/-/blob/v5.5.0/Documentation/release/ParaView-5.5.0.md).
## Tecplot reader
......
......@@ -10,7 +10,7 @@ Major changes made since ParaView 5.6.0 are listed in this document. The full li
The CMake build sub-system for ParaView has been completely redone and updated to effectively use the latest enhancements in CMake. Following these improvements, developers should see a vast improvement in CMake configure and generate times due to minimizing of the number of generated configuration files that were previously used to track module-related information. Now, all of that information is associated with the targets themselves. Furthermore, modules now respect private and
public dependencies between modules including propagation of include paths. That improves build times as it avoids leaking include paths and minimizes potential for private includes from clobbering other modules. Please be advised that these changes have resulted in changes
to available CMake options when building ParaView [Read more...](https://gitlab.kitware.com/paraview/paraview/blob/master/Documentation/dev/build.md).
to available CMake options when building ParaView [Read more...](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Documentation/dev/build.md).
Guidelines for updating ParaView plugins and ParaView-based
applications will be enumerated in a future transition guide document.
......@@ -25,7 +25,7 @@ This version of ParaView does not support the building of Catalyst editions. A C
## Updated third-party dependencies
ParaView and VTK depend on a number of open source third-party libraries. ParaView 5.7.0 has the latest known stable versions of third-party libraries. For details and specific version numbers of third-party libraries that ParaView now depends on, please see the [list of updates in VTK](https://gitlab.kitware.com/vtk/vtk/issues/17608) and [ParaView](https://gitlab.kitware.com/paraview/paraview/issues/19045).
ParaView and VTK depend on a number of open source third-party libraries. ParaView 5.7.0 has the latest known stable versions of third-party libraries. For details and specific version numbers of third-party libraries that ParaView now depends on, please see the [list of updates in VTK](https://gitlab.kitware.com/vtk/vtk/-/issues/17608) and [ParaView](https://gitlab.kitware.com/paraview/paraview/-/issues/19045).
## Enabling rendering with Mesa
......
......@@ -650,7 +650,7 @@ void pqParaViewMenuBuilders::buildHelpMenu(QMenu& menu)
#endif
// Bug report
QString bugReportURL = QString("https://gitlab.kitware.com/paraview/paraview/issues/"
QString bugReportURL = QString("https://gitlab.kitware.com/paraview/paraview/-/issues/"
"new?issue[title]=Bug&issue[description]="
"OS: %1\nParaView Version: %2\nQt Version: %3\n\nDescription")
.arg(QSysInfo::prettyProductName())
......
......@@ -58,7 +58,7 @@ pqTextureComboBox::pqTextureComboBox(vtkSMProxyGroupDomain* domain, QWidget* par
QObject::connect(this, SIGNAL(currentIndexChanged(int)), this, SLOT(onCurrentIndexChanged(int)));
// DomainModifiedEvent is never invoked by ProxyGroupDomain
// https://gitlab.kitware.com/paraview/paraview/issues/19062
// https://gitlab.kitware.com/paraview/paraview/-/issues/19062
// We have to monitor proxy creation
pqServerManagerObserver* observer = pqApplicationCore::instance()->getServerManagerObserver();
QObject::connect(observer, SIGNAL(proxyRegistered(const QString&, const QString&, vtkSMProxy*)),
......
......@@ -74,7 +74,7 @@ If you have found a bug:
3. Finally, if the issue is not resolved by the above steps, open
an entry in the [ParaView Issue Tracker][].
[ParaView Issue Tracker]: https://gitlab.kitware.com/paraview/paraview/issues
[ParaView Issue Tracker]: https://gitlab.kitware.com/paraview/paraview/-/issues
Contributing
============
......
......@@ -1440,7 +1440,7 @@ Json::Value vtkConvertXMLElementToJSON(
// not needed, because `vtkIdType` represents plain (Int32)
// integers in this case.
//
// See: https://gitlab.kitware.com/paraview/paraview/issues/16938
// See: https://gitlab.kitware.com/paraview/paraview/-/issues/16938
#ifdef VTK_USE_64BIT_IDS
template <>
Json::Value vtkConvertXMLElementToJSON<vtkIdType>(
......
......@@ -685,13 +685,13 @@ XMLs to JSON.
###Changes to `pqViewFrame`###
Commit [afaf6a510](https://gitlab.kitware.com/paraview/paraview/commit/afaf6a510ecb872c49461cd850022817741e1558)
Commit [afaf6a510](https://gitlab.kitware.com/paraview/paraview/-/commit/afaf6a510ecb872c49461cd850022817741e1558)
changes the internal widgets created in `pqViewFrame` to add a new `QFrame` named
**CentralWidgetFrame** around the rendering viewport. While this shouldn't break any
code, this will certainly break tests since the widgets have changed. The change to the testing
XML is fairly simple. Just add the **CentralWidgetFrame** to the widget hierarchy at the appropriate
location. See the original
[merge request](https://gitlab.kitware.com/paraview/paraview/merge_requests/167)
[merge request](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/167)
for details.
###Changes to `vtkSMProxyIterator`###
......
......@@ -1377,7 +1377,7 @@ configuration type, which may look something like
`C:\Users\MyUser\ParaView-v4.2.0-build\lib\Release\vtkPVAnimation-pv4.2.lib`.
[ParaView Guide]: http://www.kitware.com/products/books/paraview.html
[core readers]: https://gitlab.kitware.com/paraview/paraview/blob/87babdbeab6abe20aac6f8b2692788abc6bb20ac/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml#L158-179
[core readers]: https://gitlab.kitware.com/paraview/paraview/-/blob/87babdbeab6abe20aac6f8b2692788abc6bb20ac/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml#L158-179
[pqPropertyWidget]: https://kitware.github.io/paraview-docs/nightly/cxx/classpqPropertyWidget.html
[pqPropertyWidgetDecorator]: https://kitware.github.io/paraview-docs/nightly/cxx/classpqPropertyWidgetDecorator.html
[QActionGroup]: https://doc.qt.io/qt-5/qactiongroup.html
......
......@@ -4,9 +4,9 @@
# paraview-5.6.
# They are API-compatible with paraview-5.5 but not ABI compatible.
#
# https://gitlab.kitware.com/vtk/vtk-m/merge_requests/1166
# https://gitlab.kitware.com/paraview/paraview/merge_requests/2433
# https://gitlab.kitware.com/paraview/paraview/merge_requests/2436
# https://gitlab.kitware.com/vtk/vtk-m/-/merge_requests/1166
# https://gitlab.kitware.com/paraview/paraview/-/merge_requests/2433
# https://gitlab.kitware.com/paraview/paraview/-/merge_requests/2436
#
--- ParaView-v5.5.0/VTK/ThirdParty/vtkm/vtk-m/CMake/VTKmDetermineVersion.cmake.orig 2018-04-06 22:03:33.000000000 +0200
+++ ParaView-v5.5.0/VTK/ThirdParty/vtkm/vtk-m/CMake/VTKmDetermineVersion.cmake 2018-04-23 12:00:23.708544206 +0200
......
......@@ -435,7 +435,7 @@ bool vtkCGNSWriter::vtkPrivate::WriteFieldArray(write_info& info, const char* so
else // 1-component field data.
{
// force to double precision, even if data type is single precision,
// see https://gitlab.kitware.com/paraview/paraview/issues/18827
// see https://gitlab.kitware.com/paraview/paraview/-/issues/18827
for (vtkIdType t = 0; t < da->GetNumberOfTuples(); ++t)
{
double* tpl = da->GetTuple(t);
......
Markdown is supported
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