From f9c2b56518f681b31abe8a431886bfee44571106 Mon Sep 17 00:00:00 2001 From: Carl Baldwin Date: Thu, 14 Apr 2016 09:39:11 -0600 Subject: [PATCH] Avoid referencing code from master branch I clicked on this link while reading the plugin development section in the effective neutron guide. I wasn't sure it linked me to the right thing because it currently links to a blank line. I figured that it was just a line off but I wasn't sure because the link is to the master branch, which can change. This patch changes master to the short commit id of the commit that added this link in the first place. This way, it'll always link to what it originally linked to. If contents move around on master by adding code to the file or refactoring or whatever, it might still cause some confusion but at least we'll know what it was originally intended to point to without doubt. Change-Id: I13a10e10a31b88cb6f030ca644ca20e0bf14012c --- doc/source/devref/effective_neutron.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/devref/effective_neutron.rst b/doc/source/devref/effective_neutron.rst index 2ea2c925547..382516c4dc4 100644 --- a/doc/source/devref/effective_neutron.rst +++ b/doc/source/devref/effective_neutron.rst @@ -75,7 +75,7 @@ Document common pitfalls as well as good practices done during plugin developmen there is an agent on the other side of the message broker that interacts with the server. Plugins may not rely on `agents `_ at all. * Be mindful of required capabilities when you develop plugin extensions. The - `Extension description `_ provides the ability to specify the list of required capabilities + `Extension description `_ provides the ability to specify the list of required capabilities for the extension you are developing. By declaring this list, the server will not start up if the requirements are not met, thus avoiding leading the system to experience undetermined behavior at runtime.