Migration

- Updated repository URL.

DEVELOPER

@@ -137,7 +137,7 @@ Unit Tests Needed
 
   The tests are mainly written in Perl, and all use TAP.  Here is how to get the
   code and run the test suite:
-     git clone git://tasktools.org:task.git
+     git clone https://git.tasktools.org/scm/tm/task.git
      cd task.git
      git checkout 2.4.0
      cmake .
@@ -159,7 +159,7 @@ Unit Tests Needed
   If you make a habit of running the test suite, consider downloading the
   vramsteg utility to show a colorful progress bar, from:
 
-    git://tasktools.org/vramsteg.git
+    https://git.tasktools.org/scm/ut/vramsteg.git
 
   Tests needed:
 

EXPOSITION

@@ -154,7 +154,7 @@ Test Suite
   many platforms. Code changes are automatically detected, propagated, built and
   tested on a variety of participating platforms. Grid testing results are here:
 
-    http://tasktools.org/tinderbox/taskwarrior-2.3.0.html
+    http://tasktools.org/tinderbox/taskwarrior-2.4.0.html
 
   When making code changes, it is important that the test suite be run to verify
   that functionality was not broken.

doc/man/task-color.5.in

@@ -325,7 +325,7 @@ The official site at
 
 .TP
 The official code repository at
-<git://tasktools.org/task.git/>
+<https://git.tasktools.org/scm/tm/task.git>
 
 .TP
 You can contact the project by writing an email to

doc/man/task-faq.5.in

@@ -360,7 +360,7 @@ The official site at
 
 .TP
 The official code repository at
-<git://tasktools.org/task.git/>
+<https://git.tasktools.org/scm/tm/task.git>
 
 .TP
 You can contact the project by writing an email to

doc/man/task-sync.5.in

@@ -163,7 +163,7 @@ The official site at
 
 .TP
 The official code repository at
-<git://tasktools.org/task.git/>
+<https://git.tasktools.org/scm/tm/task.git>
 
 .TP
 You can contact the project by writing an email to

doc/man/task-tutorial.5.in

@@ -3104,7 +3104,7 @@ The official site at
 
 .TP
 The official code repository at
-<git://tasktools.org/task.git/>
+<https://git.tasktools.org/scm/tm/task.git>
 
 .TP
 You can contact the project by writing an email to

doc/man/task.1.in

@@ -1105,7 +1105,7 @@ The official site at
 
 .TP
 The official code repository at
-<git://tasktools.org/task.git/>
+<https://git.tasktools.org/scm/tm/task.git>
 
 .TP
 You can contact the project by emailing

doc/man/taskrc.5.in

@@ -1059,8 +1059,6 @@ Presence/absence of UDA data.
 The coefficients reflect the relative importance of the various terms in the
 urgency calculation.  These are default values, and may be modified to suit your
 preferences, but it is important that you carefully consider any modifications.
-See the original RFC-31 for complete details at:
-http://tasktools.org/gitweb/gitweb.cgi?p=rfc.git;a=blob_plain;f=rfc31-urgency.txt;hb=HEAD
 
 .SS SHADOW FILE
 
@@ -1399,7 +1397,7 @@ The official site at
 
 .TP
 The official code repository at
-<git://tasktools.org/task.git/>
+<https://git.tasktools.org/scm/tm/task.git>
 
 .TP
 You can contact the project by emailing

doc/man/tasksh.1.in

@@ -172,7 +172,7 @@ The official site at
 
 .TP
 The official code repository at
-<git://tasktools.org/task.git/>
+<https://git.tasktools.org/scm/tm/task.git>
 
 .TP
 You can contact the project by emailing

package-config/osx/README

@@ -26,7 +26,7 @@ Note: This is being written from the OSX 10.6 perspective, and may therefore
     clone of the repository, because we will do (locally) destructive things
     to it.
 
-    $ git clone git://tasktools.org/task.git ~/task-package.git
+    $ git clone https://git.tasktools.org/scm/tm/task.git ~/task-package.git
     ...
     $ cd ~/task-package.git
 
@@ -36,8 +36,8 @@ Note: This is being written from the OSX 10.6 perspective, and may therefore
     commit, via a tag.  Note that while 1.9.2 is a branch name, v1.9.2 is a tag
     name.
 
-    $ git checkout 1.9.2
+    $ git checkout 2.4.0
-    $ git reset --hard v1.9.2
+    $ git reset --hard v2.4.0
 
     If there is an error in this step, stop, capture the output, and report the
     errors.