From 2c6f12f3757a3cad9fb5567d4e52bf5f372c0bf1 Mon Sep 17 00:00:00 2001 From: YAMAMOTO Takashi Date: Wed, 3 Dec 2014 12:53:14 +0900 Subject: [PATCH] template.rst: Fix build failure Fix build failure: "WARNING: Literal block expected; none found." Change-Id: Ic3234d11bdfcddb59f4c585fd6bb36ee4baa14a3 --- specs/template.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specs/template.rst b/specs/template.rst index 7e9c97fbd..2bb217e0c 100644 --- a/specs/template.rst +++ b/specs/template.rst @@ -19,7 +19,7 @@ If your specification proposes any changes to the Neutron REST API such as changing parameters which can be returned or accepted, or even the semantics of what happens when a client calls into the API, then you should add the APIImpact flag to the commit message. Specifications with -the APIImpact flag can be found with the following query:: +the APIImpact flag can be found with the following query: https://review.openstack.org/#/q/status:open+project:openstack/neutron-specs+message:apiimpact,n,z