From 140ff7184118387bac442a67e151f4c529e7210a Mon Sep 17 00:00:00 2001
From: Michael Hanselmann <hansmi@google.com>
Date: Thu, 11 Aug 2011 12:18:59 +0200
Subject: [PATCH] Fix epydoc error in rlib2.py
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

I blindly assumed epydoc would use normal reST, but turns out it uses
its own β€œepytext” in our configuration. Since the latter doesn't support
blockquotes, I just make the paragraph a literal block.

Signed-off-by: Michael Hanselmann <hansmi@google.com>
Reviewed-by: Iustin Pop <iustin@google.com>
---
 lib/rapi/rlib2.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/rapi/rlib2.py b/lib/rapi/rlib2.py
index d6aeb50c3..fc5c6ec20 100644
--- a/lib/rapi/rlib2.py
+++ b/lib/rapi/rlib2.py
@@ -32,7 +32,7 @@ In the context of this module POST on ``/2/instances`` to change an existing
 entity is legitimate, while PUT would not be. PUT creates a new entity (e.g. a
 new instance) with a name specified in the request.
 
-Quoting from RFC2616, section 9.6:
+Quoting from RFC2616, section 9.6::
 
   The fundamental difference between the POST and PUT requests is reflected in
   the different meaning of the Request-URI. The URI in a POST request
-- 
GitLab