Signed-off-by: Alan Coopersmith <[email protected]>
---
 randrproto.txt     | 2 +-
 specs/XI2proto.txt | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/randrproto.txt b/randrproto.txt
index faafc4c..88f06cc 100644
--- a/randrproto.txt
+++ b/randrproto.txt
@@ -3427,4 +3427,4 @@ Bibliography
 
 [RENDER]
        Packard, Keith, "The X Rendering Extension", work in progress,
-       http://cgit.freedesktop.org/xorg/proto/renderproto/tree/renderproto.txt
+       
https://gitlab.freedesktop.org/xorg/proto/xorgproto/raw/master/renderproto.txt
diff --git a/specs/XI2proto.txt b/specs/XI2proto.txt
index 697dd89..440b0d0 100644
--- a/specs/XI2proto.txt
+++ b/specs/XI2proto.txt
@@ -574,7 +574,7 @@ that pointer's direction, the movement of the pointer is 
clamped to the x or
 y coordinate of the barrier, whichever applies. For a description of pointer
 barriers and barrier creation and destruction see the XFixes protocol
 specification v 5.0 or later.
-http://cgit.freedesktop.org/xorg/proto/fixesproto/plain/fixesproto.txt
+https://gitlab.freedesktop.org/xorg/proto/xorgproto/raw/master/fixesproto.txt
 
 A pointer hitting a blocking barrier creates a new barrier event sequence,
 identified by a unique event ID. A new event ID is assigned when the pointer
-- 
2.15.2

_______________________________________________
[email protected]: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel

Reply via email to