[build-path-prefix-map-spec] 50/50: Update URLs

[Ximin Luo]

This is an automated email from the git hooks/post-receive script.

infinity0 pushed a commit to branch master
in repository build-path-prefix-map-spec.

commit a57ec9187e6f5800ac71972b3665b717d1ef5a6e
Author: Ximin Luo <infinity0 at debian.org>
Date:   Fri Mar 10 16:15:22 2017 +0100

    Update URLs
---
 spec.in.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/spec.in.rst b/spec.in.rst
index 156e115..244bda7 100644
--- a/spec.in.rst
+++ b/spec.in.rst
@@ -167,7 +167,7 @@ Notes and links
     <https://wiki.debian.org/ReproducibleBuilds/BuildPathProposal#Implementation_notes>`_.
     Example source code is also available there, as well as in runnable form in
     `our git repository
-    <https://anonscm.debian.org/git/reproducible/standards.git/tree/build-path-prefix-map>`_.
+    <https://anonscm.debian.org/cgit/reproducible/build-path-prefix-map-spec.git>`_.
     The test vectors from this document's appendix are also available there.
 
 .. [3] This is to make it easier for producers to append values, e.g. as in
@@ -203,7 +203,7 @@ Windows system strings
 Windows strings are commonly advertised as "UTF-16", however for environment
 variable values and filesystem paths the system APIs do not enforce validity of
 the 16-bit strings passed to it. In other words, it is UCS-2, but this term `is
-deprecated (no HTTPS) <http://unicode.org/faq/utf_bom.html#utf16-1>`_.
+deprecated (no HTTPS) <http://unicode.org/faq/utf_bom.html#utf16-11>`_.
 
 So in practice, user code should not assume that these system strings are valid
 UTF-16, and should be able to deal with invalid UTF-16 strings. The easiest way
@@ -273,7 +273,7 @@ Test vectors
 
 Here are test vectors for implementations to check their correctness. They are
 also available as part of an executable test suite in `our git repository
-<https://anonscm.debian.org/git/reproducible/standards.git/tree/build-path-prefix-map>`_.
+<https://anonscm.debian.org/cgit/reproducible/build-path-prefix-map-spec.git>`_.
 They are intended for guidance and *not* as a substitute to the above
 specification. In particular, it may be possible to match the behaviour
 described below exactly but still violate the specification.

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/build-path-prefix-map-spec.git