summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTristan Van Berkom <tristan.vanberkom@codethink.co.uk>2018-08-25 17:44:26 +0900
committerTristan Van Berkom <tristan.vanberkom@codethink.co.uk>2018-08-25 17:44:26 +0900
commit369bec0c27c2b40d6d928940749036cb317f6613 (patch)
tree0c6c2968dc35ba1ed1b64510c9a2e4d1fa3b0ab9
parent23b01f244af12d7b60b92c9bb5f4578a794a6307 (diff)
downloadbuildstream-369bec0c27c2b40d6d928940749036cb317f6613.tar.gz
doc/source/developing/workspaces.rst: Some whitespace fixes
Some whitespace changes to follow the style regarding empty lines between sections.
-rw-r--r--doc/source/developing/workspaces.rst5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/source/developing/workspaces.rst b/doc/source/developing/workspaces.rst
index c2e8703f8..b5ed64b2c 100644
--- a/doc/source/developing/workspaces.rst
+++ b/doc/source/developing/workspaces.rst
@@ -4,7 +4,6 @@
Workspaces
==========
-
In this section we will cover the use of BuildStream's workspaces feature when devloping on a
BuildStream project.
@@ -26,7 +25,6 @@ make changes to the source code of Buildstream elements by making use of
BuildStream's workspace command.
-
Opening a workspace
-------------------
First we need to open a workspace, we can do this by running
@@ -38,12 +36,12 @@ This command has created the workspace_hello directory in which you can see
the source for the hello.bst element, i.e. hello.c and the corresponding
makefile.
-
You can view existing workspaces using
.. raw:: html
:file: ../sessions/developing-workspace-list.html
+
Making code changes
-------------------
Let's say we want to alter the message printed when the hello command is run.
@@ -67,6 +65,7 @@ This gives us the new message we changed in hello.c.
From this point we have several options. If the source is under version control
we can commit our changes and push them to the remote repository.
+
Closing your workspace
----------------------
If we want to close the workspace and come back to our changes later, we can