From 2f3324cbeeada97f94105d9c8ce902f496e34dd3 Mon Sep 17 00:00:00 2001 From: Mukund Sivaraman Date: Thu, 12 Sep 2013 12:51:49 +0530 Subject: [PATCH] [3109] Re-justify paragraph (after changes in previous commits) --- doc/devel/contribute.dox | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/doc/devel/contribute.dox b/doc/devel/contribute.dox index 949c4ba758..f408c1e547 100644 --- a/doc/devel/contribute.dox +++ b/doc/devel/contribute.dox @@ -88,14 +88,14 @@ or ./configure --with-gtest-source=/path/to/your/gtest/dir @endcode -There are other useful switches which can be passed to configure. It is always a good -idea to use \c --enable-logger-checks, which does sanity checks on logger -parameters. If you happen to modify anything in the documentation, use -\c --enable-generate-docs. If you are modifying DHCP code, you are likely -to be interested in enabling the MySQL backend for DHCP. Note that if the backend -is not enabled, MySQL specific unit-tests are skipped. From that -perspective, it is useful to use \c --with-dhcp-mysql. For a -complete list of all switches, use: +There are other useful switches which can be passed to configure. It is +always a good idea to use \c --enable-logger-checks, which does sanity +checks on logger parameters. If you happen to modify anything in the +documentation, use \c --enable-generate-docs. If you are modifying DHCP +code, you are likely to be interested in enabling the MySQL backend for +DHCP. Note that if the backend is not enabled, MySQL specific unit-tests +are skipped. From that perspective, it is useful to use +\c --with-dhcp-mysql. For a complete list of all switches, use: @code ./configure --help